navigation bar

search

Greetings Visitor!

Welcome to JRNG Shop!

Please browse through our products at the top
navigation bar menu under 'Products' section.



* [ Announcement ] *
-

Saturday, May 13, 2017

Windows 10 build 15063 DISM fix workaround

When issuing the command "DISM /Online /Cleanup-Image /RestoreHealth" when building reference image, it will get Error: 0x800f081f and no matter what /source install.wim you use, it will get the same error.

workaround:
1. give full control permission to administrators to the below 2 registry keys.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

2. delete the 2 registry keys

3. issuing the command "DISM /Online /Cleanup-Image /RestoreHealth" again and it should not get any error.


Saturday, April 08, 2017

SCCM Client install failed in Primary site server

Encounter error while installing SCCM Client in Primary site server. Error is "Setup was unable to register the CCM_Service_HostingConfiguration endpointThe error code is 80041002"
















Resolution:
1. Remove Management Point role from primary site server. Check mpsetup.log and restart
2. Install the SCCM Client by launching cmd as administrator
3. Change the directory to the \client directory. For example, change the directory to C:\Program Files\Microsoft Configuration Manager\Client
4. ccmsetup.exe SMSSITECODE=[sitecode] SMSMP=[fqdn of primary site server name] FSP=[fqdn of primary site server name] PATCH=%CD%\hotfixes\client\x64\[filename of the patch].msp
5. check ccmsetup.log
6. Once SCCM Client installed successful, add Management Point role back to primary site server. check mpsetup.log

Sunday, April 02, 2017

Move DP Content using Content Library Transfer tool

Example Scenario:
When installing a Distribution Point role, you specify the content locations for the content library and package share to D drive. Then one day, D drive was full, it will distribute the content to the disk with the next most free disk space, example C drive.

Now you free up some space of D drive and want to move the distributed content back from C to D drive.

Content Library Transfer tool is use to move the content.

Pre-Requisite:
1. Download the toolkit from here and install on the server running the distribution point role.
2. Your account must have administrative permission on the distribution point server.
3. The tool must run locally on the distribution point server.

Steps:
1. The ContentLibraryTransfer.exe will be installed in C:\Program Files (x86)\ConfigMgr 2012 Toolkit R2\ServerTools
2. Launch cmd.exe as administrator
3. Run the follow commands
- cd "C:\Program Files (x86)\ConfigMgr 2012 Toolkit R2\ServerTools"
- ContentLibraryTransfer.exe -SourceDrive C -TargetDrive D > C:\temp\contentlibrarytransfer.log
- If the content transfer is successful, you should find the line in the log file which reads "Content Library Transfer is now complete !!".

Once the content transfer is completed successfully, NO_SMS_ON_DRIVE.SMS file is created on the source drive, in this case is C drive. This means the ContentLibraryTransfer tool will not copy the content library to this drive anymore.

Also check the current Content Library path using registry, it should be D:\SCCMContentLib, you can navigate to HKLM\SOFTWARE\Microsoft\SMS\DP\ContentLibraryPath.