Migrating Clients from SMS 2003 to SCCM 2012 R2. Best method?

I have set up a new SCCM 2012 R2 server to replace our existing SMS 2003.
Our client systems (all Windows 7 SP1 x64 and x86) still have the SMS 2003 client installed but I would like to move them over to the SCCM 2012 R2 server now. I know there are several methods for installing the SCCM client (manual, push, group policy) but
none of these provide a way to uninstall the old client.
Is there a best practice or commonly used process for doing this? Should I be getting rid of the SMS client first by logon script or some other method and the pushing the SCCM client or some other way? Thank you for any advice.

More info:
Can I manage SMS 2003 clients with System Center 2012 Configuration Manageror migrate SMS 2003 sites and clients to System Center 2012 Configuration Manager?
http://technet.microsoft.com/library/gg682088.aspx#FAQ_Migration
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

SQL Query (Migrating report from SMS 2003 and SCCM 2012R2)

Hello everyone,
I solicit you because I have to work on migrating reports from SMS 2003 and SCCM 2012 R2.
The following SQL query causes me some problems:
SELECT DISTINCT SYS.Netbios_Name0 AS Computer, (SELECT SUM(ProcAddtl.NumberOfLogicalProcessors0) FROM v_GS_Processor_Addtl0 ProcAddtl WHERE ProcAddtl.ResourceID=SYS.ResourceID) [Cores], CS.NumberOfProcessors0 AS CPU, CPU.MaxClockSpeed0 As Speed, CPU.Name0, MEMORY.TotalPhysicalMemory0/1024 AS [RAM Mb], (SELECT LDISKS.Name0 + '=' + CONVERT(varchar(15), LDISKS.Size0/1024) + ' | ' as 'data()' FROM v_GS_LOGICAL_DISK LDISKS WHERE LDISKS.ResourceID=SYS.ResourceID AND (LDISKS.Name0='C:' OR LDISKS.Name0='D:') ORDER BY LDISKS.Name0 FOR xml path('')) [Logical Disk (Gb)], (SELECT LDISKS.Name0 + '=' + CONVERT(varchar(15), LDISKS.FreeSpace0/1024) + ' | ' as 'data()' FROM v_GS_LOGICAL_DISK LDISKS WHERE LDISKS.ResourceID=SYS.ResourceID AND (LDISKS.Name0='C:' OR LDISKS.Name0='D:') ORDER BY LDISKS.Name0 FOR xml path('')) [Free Space(Gb)],CS.Manufacturer0 AS Manufacturer, CS.Model0, OS.Caption0 AS 'OS', (SELECT CONVERT(varchar(10), NIC.Index0) + '=' + NIC.IPAddress0 + ' | ' as 'data()' FROM v_GS_NETWORK_ADAPTER_CONFIGUR NIC WHERE NIC.ResourceID=SYS.ResourceID FOR xml path('')) [Network], (SELECT Count(Name0) FROM v_GS_SCSI_CONTROLLER SCSI WHERE SCSI.ResourceID=SYS.ResourceID AND SCSI.Name0 Like '%Qlogic%') [# FC HBA], INFONOYAU.RoleServeur0 AS Role, INFONOYAU.Zone0 AS Zone
FROM v_R_System SYS
LEFT JOIN v_GS_COMPUTER_SYSTEM CS ON CS.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_PROCESSOR CPU ON CPU.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_X86_PC_MEMORY MEMORY ON MEMORY.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_OPERATING_SYSTEM OS ON OS.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_Informations_Noyau0 INFONOYAU ON INFONOYAU.ResourceID = SYS.ResourceID
LEFT JOIN v_FullCollectionMembership COL ON COL.ResourceID = SYS.ResourceID
WHERE COL.CollectionID = @CollectionID ORDER BY SYS.Netbios_Name0
Can a charitable soul help me to migrate this query to a SCCM 2012R2 report?

The following SQL query causes me some problems:
Why? What's happening?
Torsten Meringer | http://www.mssccmfaq.de

Best practice for client migration from SMS 2003 to SCCM 2012 R2?

Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
Options are:
1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
2. Simply push SCCM client from console installing over existing SMS 2003 client.
I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
Appreciate any feedback. Thank you.

Hi,
>>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
Best Regards,
Joyce

Crypt acquire context failed with 0x8009000f after upgrade from sms 2003 to SCCM 2007 SP1

I've upgraded clients from SMS 2003 SP3 to SCCM 2007 SP1.
In the SCCM console some ressources are showing as not being client.
If I look on the machine, I can see that client is installed but the client cannot communicate with the management point.
CCMEXEC.log shows the following error message :
Crypt acquire context failed with 0x8009000f.
Failed to create certificate 8009000f CcmExec 21/04/2009 9:49:10 1948 (0x079C)
CCMDoCertificateMaintenance() failed (0x8009000f).
So, the issue is related to certificate
If I go to C:\documents and settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys and delete the file begining by 19c5cf... and then restart the client the problem is solved.
Can someone explain what is happening ?
What can I do to prevent this problem
Kind regards

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)
I just added another account to the security (local Administrators) for the key which starts with 19c5cf...
and restarted the SMS AGENT HOST SERVICE.
Thats also resolved the problem. (NETWORK was the only security account on the key file).

Client PC migration fails from SBS 2003 to SBS 2012 Essentials

Please check out this entire message before making an assumption about what it says, thanks.
Our old SBS 2003 Server hard failed a few weeks ago.
Rather than repair it, we ordered a new server with SBS 2012 Essentials and loaded the backup data from the old server.
The Server is just fine. We are having no issues whatsoever with the server. I kept the old domain name and server name.
The Client Computers, some Win7 some Win8.1, have turned into a nightmare to re-connect.
What happens is, the user can log in, but has no files in desktop, downloads or documents, nothing has been migrated:
The process I'm using is this:
1> I take them off the old domain and set them up as workgroup: NOGROUP... that works fine.
2> I bring up http://SERVERNAME/connect and begin installing the server software, no problem yet...
        >> This goes to a point where it asks for a restart, followed by a lot more waiting.
        >> Eventually it crashes with a message I have, unfortunately, not documented (sorry).
3> When I restart the PC, I'm able to log into the user account : DOM\username, but none of the users files are there.
Looking at the file tree at C:\Users I see a folder structure like this:
C:\Users
        |_ _client.setup_ (essentially empty)
        |_ username         (the old account... and yes, it has all of the files and app data)
        |_ username.DOM (the new account, but essentially empty)
It appears that the setup was supposed to migrate 'username' thru '_client.setup_ into 'username.DOM' but failed.
I can move all of the data from 'username' to 'username.DOM' to solve the data and files problem.
But the AppData folder cannot be moved in its entirety (I tried, and it clobbers the user completely), I have to manually transfer files from 'username\AppData' folders (Local, LocalLow and Roaming) making sure to transfer only the files that don't exist
in the 'username.DOM\Appdata' folders.
I realize that this process leaves me with a 'Less Than Perfect' AppData setup.
Since I have many Clients left to convert, I'd like to know if I'm doing something wrong, or how to make it right.

With a new server with a new domain you have started down the right path. Disjoin and the http:// technique should have worked, but we can address that when you can give us more info.
When joining a new domain the old users profiles get blocked by security to the new users. But the local admin or the domain admin should have access. The way I do it is to copy out the required data from the old profile to a safe place then
copy it back to the new profile when finished. But there are profile migration wizards, one of them at
www.forensit.com, that work very well.
As for the system crash when you did the join... please see if you can get the message, and then examine the logs in both the server and the client.   For the server, look here:
http://blogs.technet.com/b/sbs/archive/2014/09/30/windows-server-essentials-log-files.aspx
For the client, scroll down in the link above to the section about client side logs.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

System Management container already existing from SMS 2003

I am going to be introducing a new SCCM 2012 R2 server in our domain which has an existing SMS 2003 server. The first part of the SCCM 2012 R2 preparation is (from my understanding) is to create the "System Management" container using ADSIEdit
and give permission to the service account you create for SCCM.
As we already have SMS 2003 this container exists in our Active Director. Given this what is the proper procedure? Do I simply give permission for this container to the SCCM service account and that is it? What about the already existing items in this container
for our existing SMS server, will they be adversely affected or conflict with the newly created items?

Yes, simply assign permissions for your ConfigMgr 2012 site system(s) to that container. It won't touch the existing objects.
Do pay attention to overlap in boundaries, inc ase you use the boundaries for auto site assignment. See also:
http://social.technet.microsoft.com/Forums/en-US/18b93c00-1a6a-48bc-b19f-f17bfbcffb0f/sms-2003-and-sccm-2012-overlapping-boundaries?forum=configmanagerdeployment
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via SCCM 2007 PACKAGE

I can migrate sccm clients from sccm 2007 to sccm 2012 using sccm 2007 package with sccm 2012 client?
Thanks!
Atenciosamente Julio Araujo

Thanks for help me Peter and Torsten but this documentation says:
"You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client."
I Need migrate clients from sccm 2007 to sccm 2012 r2 and
I thought ofcreate a package in sccm 2007 with a sccm 2012 client.
Atenciosamente Julio Araujo

Migrating from DHCP 2003 to DHCP 2012

Hi,
i'm planning to migrate from DHCP 2003 to DHCP 2012 or DHCP 2012 R2 failover.
Saw those instructions:
extract the configuration in .TXT
netsh dhcp server export c:\temp\dhcp.txt all
copy this file on your server 2012 in temp or elsewhere
import the configuration with this command
netsh dhcp server import c:\temp\dhcp.txt all
if you have the error "TLS supported but not configured"
remove all the option in "Server Option" like 003 Router 006 DNS SERVERS and put it back after doing the import
now i have some questions:
1. is it recommended to build 2 2012 DHCP configured as failover on virtual machines ? (hyper-V)
2. do those dhcp servers have to or recommended to be DNS also or can they be only DHCP servers ?
3. my AD functionality level is 2003 - is it a problem for this migration ?
4. virtual or physical ? whats is recommended ?
5. any other considerations ?
TNX

Hi,
Virtual or physical will both work. It doesn't matter, as long as the two servers can communicate with each other.
You do not need DNS installed on the same server, but you can install it without hurting anything.
I believe that the AD level has no effect because you can have DHCP failover even on workgroup computers.
-Greg
http://technet.microsoft.com/en-us/library/dn338983.aspx#specs

How To Migrate Databases From Windows 2003 32 bit to windows 2003 64 bit?

Hi,
How To Migrate Databases From Windows 2003 32 bit to windows 2003 64 bit?
Db Version: 10.2.0.2
Thanks,
Yusuf

Also see MOS Doc 403522.1 (How to Migrate Oracle 10.2 32bit to 10.2 64bit on Microsoft Windows)
HTH
Srini

Migrating Clients from SCCM 2007 to SCCM 2012 R2 via GPO

Hello.
I can do the migration of customers from SCCM 2007 to SCCM 2012 via GPO?
When I'm migrating customers from SCCM 2007 to SCCM 2012 I have to keep the boundaries of SCCM 2007 or just the SCCM 2012?
Atenciosamente Julio Araujo

For migrating the clients you can use any client deployment method that's available (see for planning your strategy: (http://technet.microsoft.com/en-us/library/gg712283.aspx).
During the client migration I would also start with migrating your boundaries. The most important thing is that you have no overlapping boundaries for site assignment when you are using auto assignment.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

How to Preserve UDA when Migrating Clients from 2012 Heirarchy to 2012 R2 Heirarchy

We are preparing to migrate 2500 workstation clients from one 2012 R2 hierarchy to another. How can we preserve UDA so that we don't have to wait for it to be automatically generated? This would impact our ability to provide support.

I would say PowerShell. Use
Get-CMUserDeviceAffinity to get the information in the old environment and use
Import-CMUserDeviceAffinity to import the information in the new environment.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Previously blocked client computers - now cannot install SCCM 2012 R2 client

Hello,
I have a Primary Site on SCCM 2012 R2. New installation of 2012 R2, not upgrade from SCCM 2007. My environment is pretty small for now, having added just few dept computers in the company.
We are using SCCM for Endpoint Security antivirus deployment. Some time ago I had not configured the Discovery methods correctly and the scep client started to install on few machines on which it was not supposed to be installed. I removed the clients then
(both remote and local uninstallation) but since the sccm client was getinng installed again - I had to Block these few machines. Now the problem is that I cannot install the scep client on these computers that have previously been blocked. I am sure the previous
block is the reason because these are about 6-7 machines and only they do not install. All others do install scep client. The installation process goes smooth on these problematic machines, ccmsetup folder gets created in C:\Windows, I follow the ccmsetup.log
and it says " <![LOG[CcmSetup is exiting with return code 0]LOG]!><time="12:33:56.415-180" date="10-08-2014" component="ccmsetup" context="" type="1" thread="3992"
file="ccmsetup.cpp:10875"> " at the end of the log which is what it is supposed to show when installation goes ok, then Ccmexec.exe process continues running but folder Microsoft Security Client in C:\Program Files never gets
created and no scep client gets installed.
I tried deleting the computers from the sccm console and discovering them anew - did not help. Tried even renaming the comp locally, after having it deleted from sccm console, then adding it anew hoping sccm will regard it as a new resource-again no good.
All these computers have the Approve, Block and Unblock buttons greyed out/inactive in console.
Has anyone had this same problem? Any ideas what can be done. Thank you.
Regards,
Hristo

Hi,
were you ever able to fix this?
I'm running in a similar issue here.
One single client was blocked, then deleted, lateron recreated (imported manually name and MAC address).
Now the client is unable to register itself in SCCM 2012 R2 (no CU yet).
Tried the usual stuff: uninstalled SCCM client, remove the entries of CCMsetup and SMS from registry, deleted the SMS certs from the computer personal
store and deleted the smscfg.ini from C:\Windows. Then re-installed the SCCM client
Client logs look fine, except ClientIDManagerStartup.log:
<![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6 ...]LOG]!><time="14:46:11.555-60" date="01-12-2015" component="ClientIDManagerStartup" context=""
type="1" thread="6320" file="regtask.cpp:1609">
<![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="14:46:12.616-60" date="01-12-2015" component="ClientIDManagerStartup" context="" type="3" thread="6320" file="regtask.cpp:1675">
On the server:
Begin validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS'   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
Completed validation of Certificate [Thumbprint 12923BCACDAE5B89547A25E54BF11E533163742F] issued to 'SMS'   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
Encountered database error while verifying headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A' (0x87d00238).   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
CCMValidateAuthHeaders failed (0x87d00238) to validate headers for client 'GUID:F3063334-69B4-471F-B158-56782E499F4A'.   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
A client is trying to re-register with an administrator revoked certificate: SMSID='GUID:F295F120-9C99-4D10-82B7-027FDD86B5F6'.   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
MP Reg: Processing completed. Completion state = 0   MP_RegistrationManager   12.01.2015 14:31:10   8600 (0x2198)
We are using HTTP for client communication.
Any ideas appreciated.
Michael

Migrating Data from MySQL to SQL Server 2012

Hi all,
I'm Migrating a database from MySQL to SQL Server 2012, using SSMA for MySQL v5.2.1258. I've got the schema migrated over and have resolved any migration issues (stored procedures / views), but when it comes to migrating over the data I'm just hitting
a wall.
None of the data is migrating and when the migration report is displayed every table has a red x against it's Status. The Output box has the following:
Data migration operation has finished.
0 table(s) successfully migrated.
0 table(s) partially migrated.
64 table(s) failed to migrate.
I've seen on the forum that someone else was having the same problem
(http://social.msdn.microsoft.com/Forums/en-US/sqlservermigration/thread/b835f4b3-3d93-42a4-9b6b-d21d3dfd8dab/)
I've set the project settings mode to default, still getting the same error and tried using both Client Side Data Migration and Server Side migration, with both giving the same result. I've tried going through the step-by-step blog as well.
I am doing something really stupid? There are 64 tables, so don't really want to try doing exports from each table and importing it into the new database.
Hope someone can help.
Cheers
Alex

Hello,
I don’t have suggestions for you, but you can try contacting the SQL Server Migration Assistant (SSMA) Team via e-mail ([email protected])
to see if they can provide a solution on this scenario.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrating users from SBS 2003 to OSX leopard Server

Hello All,
We are preparing to migrate away from SBS2003 to an OSX server setup.
Currently all clients are mac with a few bootcamped PC's onto the macintosh hardware.
We will be using kerio to migrate the mail off from exchange.
My question is if there is a way to move the current users home folders on SBS to the mac server ala replication, i heard you could make the mac server a DC and then demote it to standalone ? is this possible or does everything have to be 'built from scratch' im assuming of course EVERYTHING is reliant on OSX leopard servers DNS being setup correctly from the get go.
Any help / tips/ cavaets / would be a huge help.
Best

unanswered

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

Migrating Clients from SMS 2003 to SCCM 2012 R2. Best method?

Similar Messages

Maybe you are looking for