.
Recently I have run into an issue when migrating cm07 clients to SCCM 1610. Accoriding to MS documentation (https://docs.microsoft.com/en-us/sccm/core/migration/planning-a-client-migration-strategy) for Configuration Manager 2007 clients, advertisement run history is retained. Unfortunately that didn't work when upgrading sccm 2007 agent on Windows 7 x64. The new SCCM 1610 Agent was as a SCCM 2007 Software Package to Windows 7 x64 Clients deployed. I noticed that the registry keys "HKLM\SOFTWARE\WOW6432Node\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\System\[PackageID]" were note beeing replicated to the 64-Bit part of the registry "HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\Software Distribution\Execution History\System\[PackageID]" and tehrefore when new Agent was installed and the Client got the policy from the MP the allready installed Software would run again.
.
0 Comments
When migration SCCM object their old source path will also be migrated. If the content needs to be migrated from one old share (e.g. \\Server1\Share1) to a new share (e.g. \\Server2\Share2) then all source paths of the migrated objects (e.g. OS Images, Drivers, Driver Sackages, Software Packages) have to be changed. With the following Powershell script it is possible to do that. The script has the several parameters:
- SourceRoot (old share) - DestinationRoot (new share) - 3 switch parameters (OS, DRV and SW) With these switch parameters ist controled for which object type is the source path customised. - 1 switch parameter ListOnly With used the objects will be only listed. No changes of the source path will be done. NOTE: I assume that the folder structure has not be changed. That means that in the source path of the migrated object only its prefix has to be changed (e.g. \\ServerOld\ShareOld\... to \\ServerNew\ShareNew\...). |
Author
Write something about yourself. No need to be fancy, just an overview. Archives
November 2022
Categories
All
|