Featured post

System Center Configuration Manager and SCCM Virtual lab related blog.

SCCM client installation faulure Silverlight.exe returned failure exit code 1625 fail the installation Portal Web Site C...

Tuesday, 13 December 2016

SCCM client installation faulure Silverlight.exe returned failure exit code 1625 fail the installation

Silverlight.exe returned failure exit code 1625 fail the installation - SCCM 2012 R2 client


When previous installation or un-installation of silverlight is corrupt, this is expected error code. and client installation will fail.





Solution for this is run a cleanup for Silverlight using  commands provided below. 

_________________________________________________________________________________
reg delete HKLM\Software\Microsoft\Silverlight /f
reg delete HKEY_CLASSES_ROOT\Installer\Products\D7314F9862C648A4DB8BE2A5B47BE100 /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\D7314F9862C648A4DB8BE2A5B47BE100 /f
reg delete HKEY_CLASSES_ROOT\TypeLib\{283C8576-0726-4DBC-9609-3F855162009A} /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\install.exe /f
reg delete HKEY_CLASSES_ROOT\AgControl.AgControl /f
reg delete HKEY_CLASSES_ROOT\AgControl.AgControl.5.1 /f
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{89F4137D-6C26-4A84-BDB8-2E5A4BB71E00} /f
rmdir /s /q "%ProgramFiles%\Microsoft Silverlight"
rmdir /s /q "%ProgramFiles(x86)%\Microsoft Silverlight"

_________________________________________________________________________________


Once done you can install SCCM 2012 R2 Client successfully.
Cheers !!



Wednesday, 28 September 2016

Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests :Error on SCCM

Portal Web Site Control Manager detected PORTALWEB is not responding to HTTP requests.  The http status code and text is 401







Solution for this issue is check IIS services are running or not. If not start services. check the specified server is disabled in IIS or not. Check IIS binding. make sure IIS is configured to listen to same port on which SCCM site server is configured to communicate.either HTTP or HTTPS
mention IP Address of server while editing binding



Tuesday, 27 September 2016

Failed to locate content access is denied on SCCM

Error:Failed to locate content access is denied. when client trying to download content from DP



Above issue were resolved after testing uninstall antivirus. it did not worked even after disabling AV. but downloaded content after uninstall AV. Cause: AV were blocking few of HTTP connections !
Once clear AV blocks/excludes from blocking it, good to go !!

You may find similar issue discussion on TN Here
Share your feedback and comments below

Cheers 
Thank you for reading .

Monday, 26 September 2016

cannot connect to the rpc service on computer- Unable to connect to Hyper-v server 2012 R2 from remote Hyper-V Manager

Error: Cannot connect to RPC Service on computer "ServerName" make sure your RPC Service is running





Solution: There are many work around you can perform when there is an RPC Error .install Hyper-V RTM updates, DCOM permissions, administrator right etc-Refer (Technet forum)

However in this case correcting all above will not resolved the issue.as far as  Hyper-V Date and time is not equal to Domain controller. The moment set time and date of Hyper-V server equal to the time of Domain server, Hyper-V manager will be able to successfully connect to Hyper-V server.

Thank you for reading :)

Please provide your feedabck below if any...

How to Customize background image on SCCM 1511 OSD Task sequence

Customize background image on SCCM 1511 OSD Task sequence


Organizations prefer to have their own background image during SCCM OS Deployment.instead of below default MS MDT image. This post will help you to set your own backgound image for SCCM OS Deployment...

Pic:01-Default MDT SCCM OSD background


To change the default Image you need to replace the existing 5 image files on  MDTFiles package with your own backgroundimage. once done make sure you update the distribution points of the package.
Default Image files can be found in \\ServerName\MDTFIlespackageSource\Tools\x86\.  Image files named STEP_01 to STEP_05 need to be replaced

Once above has been done you can try booting PXE, select respective task sequence and wait for your custom background image look like below



Pic:02-Customized Background Image

Please feel free to provide your valuable feedback...

Thank you for reading :)




System Center Configuration Manager and SCCM Virtual lab related blog.