Search the Community

Hey Guys / Niall - So I manage an environment of ~10,000 workstations and ~900 servers on a single domain. A few months ago, we acquired a new company which has their own SCCM environment on a different domain. Finally, I am wrapping up a build of SCCM on a 3rd domain. The plan is to migrate all clients from the two old domains onto the new one. I have a couple of questions about this procedure so wanted to post to get opinions... 1. Migrate Many Clients to New Site Prior to Domain Change The main question is that their current plan is to migrate the domain on workstations a department at a time over a six month period. While doing so, they want to use my script to migrate each of the workstations' SCCM client while changing the domain. The last thing i want is to have 3 separate and constantly changing environments to manage, so am trying to find the best way to potentially migrate the clients from both old domains to the new one before (like few months in some cases) the domains on the workstations are changed. There's currently a one-way trust between the new domain and both old ones and don't know if I can get them to make it more flexible. Basically, I'm curious what I would need to do in order to achieve the goal above. My experience tells me the below would be needed - at least in theory: Add scope of system's OUs / containers in old domain to discovery on new site Script executed per system to change the site of the client to the new site The SCCM Network Service account to have local admin rights on all workstations (per old domain) Specific DNS records modified / changed to point to the FQDN of the new primary instead of the old ones (per old domain) Is the above all that would be required, know of any helpful posts related to this, or any suggestions / thoughts? 2. Migration of Packages, Applications, etc with New Source Path I'll be moving a lot of packages and such over to the new environment, but am now using a new "master" share for the sources of all packages, applications, etc. It's simple to migrate an SCCM package from one site to a new one, but when doing so; it retains the same source path for it. Does anyone know of a PowerShell script or overlooked options which would allow me to change just the first part of the source path for migrated packages when moving to the new site? If capable of copying the source content during the migration, that would be ideal; but if not copying it would still be faster than changing each manually. I'm considering simply exporting certain packages, then importing them back in. Will have to play with that a bit more to see how it would work. Suggestions? All 3 sites run SCCM 2012 R2 SP1 CU4. We cannot go to current branch yet due to numerous legacy apps on workstations which don't play nice with .NET 4+. Most site servers (especially on the new environment) run Windows 2012 R2. Any suggestions or comments would be appreciated. Thanks!!

Hi Everyone, I may need to be doing a migration from an older version of SCCM to SCCM 2012 and I can't really see anything online about how this would happen. Is there actually a migration path to follow, or is it basically a brand new SCCM installation?

Hey Guys / Niall - I'm in need of assistance with an issue, please. Our company is moving all systems over to a new domain over the next few months. One other change will be that the new domain will have a new SCCM environment. Since I'd rather not manage multiple environments, the plan is to migrate all workstations over to the new SCCM environment over about a week's time before migrating the domain on the systems. I've already built the new environment and all site servers on the new domain so was ready to start client migration. Changing a system to the new SCCM site and new domain works great - however - changing the client to the new SCCM site while retaining the old domain is not working. Overall, I have ~10,000 workstations on our current domain which are members of the existing SCCM site. I'm needing to migrate the clients to a new SCCM site which is on a new domain, but without changing the domain. I'm using a VBS file to change the client's site code to the new environment. Once I do, communication isn't correct, though. Client's log files show: ClientIDManagerStartup.log RegTask: Failed to refresh MP. Error: 0x8000ffff LocationServices.log: There is no AMP for site code "BCD". LsRefreshManagementPointEx failed with 0x8000ffff Failed to refresh security settings over AD with error 0x87d00215 Failed to refresh security settings over MP with error 0x8000ffff The New SCCM environment's console shows the hostname of the test system plus shows that it's a member of the old domain. It shows that "No" client is installed on the system both prior to and after the test to migrate it. Finally, below are the things I've configured in preparation prior to the test: A two-way trust exists between the old and new domains Boundary added in New SCCM environment (ip range) for test system which is assigned to a Boundary group /w assigned site code & MP SRV record added to old domain so that new site code resolves and points to FQDN of the new SCCM server's primary server Discovery methods configured to scan for systems in the old domain Both SCCM sites are HTTP (not HTTPS) Any suggestions? Thanks!!

Hi guys, I was hoping someone could provide some guidance. We are currently in the process of a forest/domain consolidation. We have two AD forests with one domain in each. We are in the process of standing up a third forest with one domain in it on 2012 R2 that we will be moving all resources and users to over the next year. I understand that i'll need to bring up a new primary site with a new Site Code in the new third forest/domain. Some other details about the SCCM 2007 environment: One Site Server running SCCM 2007 R3 One Remote SQL server running 2008 Forefront Endpoint Protection is Integrated WSUS with a remote WSUS server on 3.0 is integrated Windows OS Deployments with WIndows Deployment Services are integrated and currently configured for deploying Windows 7 Parallels Management Suite for Managing Macs is integrated We are currently deploying many applications via SCCM Updates Publisher 2011 is current integrated with SCCM on the site server. My question is, should i migrate from the existing SCCM 2007 environment to SCCM 2012 whilst still in the same forest first before migrating collections and packages etc to the new forest? Or just migrate once and migrate the SCCM 2007 forest collections and packages etc to the new 2012 R2 forest so as to not do double work? Any pros and cons either way? If anyone has done this sort of migration i would appreciate your recommendations. Thanks Joey

Hi all, We are building a new SCCM 2012 R2 on a new hardware with new site name. the existing one is so problomatic, we would like to start all over. We can recreate the software distribution from scratch. we have one primary site that holds everything including WSUS except SQL. the new Site will have SQL included with new database. I got stuck on the Discovery method. the new server is not discovering any PCs except itself. we tried Active directory, heart beat, IP range. the old server has boudries of the whole active directory. the new server was successfully added to System Management container. Log file ADForestDisc.log come back with the following when i run the discovery manual. Beginning Active Directory Forest Discovery Manager Entering function ThreadMain() Entering function CActiveDirectoryForestDiscovery::Initialize() Component SMS_AD_FOREST_DISCOVERY_MANAGER is marked active. Log verbosity level = 0 Entering function CActiveDirectoryForestDiscovery::Process() Entering function CActiveDirectoryForestDiscovery::ShouldRun() Entering function CActiveDirectoryForestDiscovery::CheckIfRunCountValueChanged() Admin requested to run discovery now. Entering function ReportForestDiscoverySuccessStatusMessage() Raising discovery success status message for forest business.com, in which we discovered 1 site(s) and 2 subnet(s). Calling ReportStatus, keys= SMS_AD_FOREST_DISCOVERY_MANAGER, 1073750724, 0 STATMSG: ID=8900 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AD_FOREST_DISCOVERY_MANAGER" SYS=server.business.com SITE=BUS PID=4516 TID=888 GMTDATE=Tue Jan 06 19:59:10.995 2015 ISTR0="business.com" ISTR1="" ISTR2="" ISTR3="" ISTR4="2" ISTR5="1" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 Entering function CActiveDirectoryForestDiscovery::UpdateForestNamesForAllSiteSystems() Trying to update forest fqdn for all site systems associated with site BUS Entering function CActiveDirectoryForestDiscovery::UpdateForestNamesForSiteSystems() Entering function CActiveDirectoryForestDiscovery::GetForestName() Trying to discover forest name for server server.business.com. Server server.business.com belongs to forest business.com. Finishing Active Directory Forest Discovery Manager thread. Do you think it is because of the current server has the same boundries? I want to test with 1 OU in the domain that has PCs don't have agent installed yet. They are in a range of IPs i could use also. If i change the boundries on the current server from Activ directory site to 2 seperate IP ranges and then create a range of IPs on the new server. Would that cause any issues to the current inventory and collections on that server? this would be like this range 1 and range 3 are on the old and range 2 in the middle on new server. Does anyone have a better way to do it? I would like to test with actual production machines for a week then start moving PCs from old to new site. Best, and appreciate any ideas.

Hello, I was hoping someone could help point me in the right direction. We are using SCCM 2007 and UDI Toolkit 12 to deploy new WIndows 7 machines through a task sequence. We are now trying to migrate from XP to Windows 7 using USMT 4.0. We are trying to do this through the PE environment. We have it successfully doing a scan state, however we run into issues when applying the new OS. I'll mention at this point we have PointSec full disk encryption running on these devices. If we do the scanstate and use the task sequence option to format and partition the disk. It fails as it says the files are protected, these are the ones protected by USMT. So all the xml files, working directory. I think it also protects areas such as boot. I've tried calling a disk part myself and doing a clean, delete of volumes and re-creating them. It then allows it to install the OS, however whenever it does its first reboot it says no OS is present. When I run diskpart its changed the volume to RAW and you cannot access the data. I've tried various combinations on running both types of formats/partitions cleans etc.. One thing I cannot make sense of is that we use the task sequence format and partition when we don't need to save data. So this just blows away XP with encryption and puts on Windows 7, i've tried using this same command but it doesn't have the same effect. Anyone able to help please? Thanks, Andy