SCCM 2012: clients from SCCM 2007 to 2012: software available instead of installed

Hi,
We have migrated some Windows 7 clients from SCCM 2007 to SCCM 2012 (in which already hundreds of working W7 clients and their apps -most of them migrated from SCCM 2007).
Now applications are shown as available instead of installed. F.e. Adobe Acrobat is installed but it shows as available.
Please advise howto correct.
J.
Jan Hoedt

Hi,
Does it show the right status after you click "Install" of an application?
Best Regards,
Joyce
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

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

How to reduce configuration cache file Quota size located in ( C:\Windows\ccmcache ) for all client from SCCM 2012 server

How to reduce configuration cache file Quota size located in ( C:\Windows\ccmcache ) for all client from SCCM 2012 server
Thanks in Advance
NTRao

Hi,
There are numerous ways to change the cache size.
You could deploy a vbscript to a collection of the devices.
On Error Resume Next
Dim UIResManager
Dim Cache
Dim CacheSize
CacheSize=20000
Set UIResManager = createobject("UIResource.UIResourceMgr")
Set Cache=UIResManager.GetCacheInfo()
Cache.TotalSize=CacheSize
Or you could use a configuration item.
http://blog.coretech.dk/heh/configuration-items-and-baselines-using-scripts-powershell-example/
You can also use the right click tools by Now Micro on a collection, if all the servers are on this would be the easiest / quickest way.
http://www.nowmicro.com/recast/right-click-tools/
http://www.david-obrien.net/2013/02/how-to-configure-the-configmgr-client/
select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like '%6.2%'
https://msdn.microsoft.com/en-us/library/windows/desktop/ms724832%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

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

SCCM 2012 clients in SCCM 2007 console

Hi
If a Windows 7 system has sccm 2012 client installed, will it get discovered in SCCm 2007 console.
Regards Sushain KApoor

If you enable AD discovery to this client, the client object will be discovered. Anyway, the SCCM 2012 clients cannot be managed by SCCM 2007. See below.
Configuration Manager also checks that you have assigned the Configuration Manager 2012 client to a site that supports the Configuration Manager client version. If you have used automatic site assignment and the client is assigned to a Configuration Manager
2007 site, the client automatically tries to find a Microsoft System Center Configuration Manager 2012 site. It first checks Active Directory Domain Services and if this is not successful (for example, the Active Directory schema is not extended or the computer
is a workgroup client), the client then checks for site information from its assigned management point. However, if the client was assigned with a specific site code and assigns to a Configuration Manager 2007 site, site assignment fails and you must manually
reassign the client to a Microsoft System Center Configuration Manager 2012 site.
Juke Chou
TechNet Community Support

Unable to install sccm client from SCCM console install client option

Hi
Unable to install client on windows 7 64 bit enterprise from sccm console. The client is discovered in sccm console with status client = NO, so we want to install sccm client from console remotely.
We cannot enable push install. my id has full access on SCCM site server SCCM product also admin rights on workstations. I am able to access net bios path SMS_<site code> of site server then client path from client machine. machine is in domain and
is boundry of sccm .
Client push install in console is diabled
Regards Sushain KApoor

Hi!
Examine the ccm.log located in <SCCM 2007 InstallationPath>\LOGS on the site server.
Best regards
Henrik

"Migrating" computer variables from 2007 to 2012

I'm in the process of migrating server clients from a 2007 to 2012 environment. The computer objects all have quite a few computer variables associated with the objects that are used during OSD task sequences.
When we do a "bare-metal" build, the computer objects are deleted and recreated, and the variables are re-populated from a reference source of truth on the new object. So no problem there.
For the migration though, I was going to install the CM2012 client (basically upgrade the client from 2007) on the servers which will then have them register with the CM2012 site. However when this happens the variables won't be applied to the 2012
computer object.
I have a few ideas to resolve this, but was wondering if anyone else had already dealt with this situation?
Some thoughts I was considering:
1: Orchestrator job that identifies "new" computer objects in 2012 and regenerates the variables from the source of truth
2. Powershell/WMI/VBScript that reads the variables from the 2007 computer object and "copies" them to the 2012 object
Any other thoughts or suggestions welcome
Scott.

Thanks Torsten, I do appreciate the replies, but I will have to respectfully disagree with the question being answered perfectly.
I had asked "...was wondering if anyone else had already dealt with this situation?". I don't actually see how an answer of "I've never done this, but use powershell" is the perfect answer. This would also not serve to help any other
people that might come across this post looking for a similar solution. I had marked that post as "helpful", but did not "mark as answer" because it didn't actually offer anything beyond what my first post already stated.
However, I'm not looking to argue. I'll post any powershell scripts or other things I end up using to help anyone else who comes across this post. There are far too many posts in the TechNet forums that just seem to get automatically closed as answered
when there is no real answer provided.

Client Migration from SCCM 2007 to SCCM 2012 via GPO

what
installation properties i can use to migrate client from sccm 2007 to sccm 2012 via gpo?
Thanks!!
Atenciosamente Julio Araujo

It all depends on your needs, I suggest that you look at this first :
All properties can be set by using GPO, it's not different from push.
http://technet.microsoft.com/en-us/library/bb632469.aspx
http://technet.microsoft.com/en-us/library/bb633010.aspx
http://social.technet.microsoft.com/wiki/contents/articles/25118.deploying-sccm-2012-r2-clients-using-group-policy.aspx
Benoit Lecours | Blog: System Center Dudes

How can I remove the SCCM 2012 client and reinstall SCCM 2007 client on all of our computers

Hello All
We have bit of a problem. Our virtual SCCM 2012 r2 server was deleted and the back solution we had in place keeps failing.
We do have our sccm 2007 server still in place but its only role was imaging as we transferred roles from one to another.
My question is now our support needs to remote into pcs but cant because the CM12 server is gone. How can I remove the 2012 client from all of our companies computers and reinstall the CM07 client so we can remote into computers again.
Thanks in advance!
Phil
Phil Balderos

Run a ccmsetup /uninstall on the clients. You may need to run via PSExec. Then push out the SCCM 2007 client via the 2k7 console.
Cheers
Paul | sccmentor.wordpress.com
Thanks Paul!
I have to do this on over 350 computers and 110 servers. How can I do it on a more massive scale?
Phil Balderos
I would check Torsten's approach first and see if the ccmsetup will uninstall the 2012 version. I'm not sure. Obviously the other way round is fine.
Using PSexec you can script this to call up a txt file of all your servers/computers and run the uninstall.
e.g.
for /f "tokens=*" %a in (computers.txt) do psexec \\%a %WINDIR%\ccmsetup\ccmsetup.exe /uninstall
If your account has privileges on all devices you won't need to add in any username/password credentials. Obviously only devices that are switched on and you have access to will run this.
Cheers
Paul | sccmentor.wordpress.com

How to force site code discovery on all the clients, Migration SCCM 2007 to SCCM 2012

HI,
I migrated SCCM 2007 to SCCM 2012 SP1, but the clients does not update the New Site Code Automatically, if I click on Discovery option the client find the new site, but I need do this automatically because are too many clients.
This registry key does not exist on client computers.
HKLM\Software\Microsoft\SMS\MobileClient\GPRequestedSiteAssignmentCode
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryInterval(Min)
HKLM\Software\Microsoft\SMS\MobileClient\GPSiteAssignmentRetryDuration(Hour)
Any Help?
Thanks.

Hello ICH-CR,
Thanks for writing to the SysCtr ConfigMgr forums.
I think there are multiple solutions to this issue and you can choose whatever fits best to your scenario.
1. While upgrading the clients from SCCM 2007 to 2012 you can assign the clients to your ConfigMgr 2012 site.
http://technet.microsoft.com/en-us/library/gg682060.aspx#BKMK_AutomaticAssignment
You just need to ensure that you have a boundary group and boundaries. More details on
http://technet.microsoft.com/en-us/library/13694ac5-8f3b-42a9-8040-b23f21c79637#BMBK_CreateBoundaryGrp
I would suggest the first method because if you create another child site, you shouldn't have to reassign the clients back again. If that is unlikely then use the following script which is method no 2
2.
http://gallery.technet.microsoft.com/scriptcenter/Change-sccm-configmgr-cf6e0327
This is a VBSCRIPT and can be ran from a network location using the PSEXC
3. Here is a smaller script
'Replace with your Site Code sSiteCode = "EnterNewSiteCode"
sMachine
= "."
set oCCMNamespace
= GetObject("winmgmts://"
& sMachine & "/root/ccm")
Set oInstance
= oCCMNamespace.Get("SMS_Client")
set oParams
= oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
oParams.sSiteCode
= sSiteCode
oCCMNamespace.ExecMethod
"SMS_Client",
"SetAssignedSite",
oParams
You can use this script as a logon script .
Anurag
Microsoft Certified Professional| Microsoft Certified Technology Specialist (ConfigMgr)
This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights.
My Blog
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SCCM 2012 client push occurs from site server or from distribution point?

I would like to set up client push in SCCM 2012 and I have a remote site with about 80 workstations that I would like to deploy the clients to using client push, but this remote site is VERY slow, as in less than 3Mbps slow. There is a remote DP located
at this site and I wanted to know if the remote workstations will be hammering my Site Server across the WAN (or MP I guess since the MP role is i installed on the Site Server) to request the client installation, or do the clients just request the client from
the Site Server or MP and then the client downloads to the remote DP and then the workstations install the SCCM 2012 client from the local DP at the remote site?
I just do NOT want the WAN link to become overwhelmed with workstation requests to install the client and have the Site Server have to respond to each and every workstation and download the SCCM 2012 client to each system over this slow WAN link.
How does the client push process actually work?
Thank you

The initial files will come from the primary site server. The rest (the biggest part) will come of the distribution point. See for a good read (even though it's more about secondary sites), this post of Jason:
http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2012 SP1 to SCCM 2012 R2 - Side by Side

Hi Friends,
Currently our SCCM infrastructure is running with a CAS site, 2 Primary Sites and 8 Secondary sites with SCCM 2012 SP1. Now we want to update this infrastructure from SCCM 2012 SP1 to 2012 R2. But we want remove CAS site and to keep only single Primary Site.
Can this be done in Side by Side migration from SCCM 2012 SP1 to SCCM 2012 R2 ? If yes then please suggest how to migrate all data (Packages/Clients) from SCCM 2012 SP1 to new infra on SCCM 2012 R2.
Thanks in advance.

You don't have many (supported) options here. Detaching a site is not possible, so indeed your only option left is to migrate. Problem here is that the supported scenario is from a ConfigMgr 2012 R2 site to a ConfigMgr 2012 R2 site (see:
http://technet.microsoft.com/en-us/library/gg682006.aspx). That means you should first upgrade your old environment before you can start with your migration.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

VBScript for logon massage from SCCM package deplyment

I want VBScript for logon message, so I can able to deploy to all of my clients from SCCM 2012
is it possible
Thanks in advance,
NTRao

Exactly as you mentioned but one time message is enough Mr.Torsten
Why would you not use a logon script for this? Why do you want to use CM12?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Remove discovered Child Domain information from SCCM

Hi,
I have Domain named X. configured well.
And a child Domain Y. which was not configured to discover in SCCM. for testing purpose i have enabled AD system discovery for this child domain and all system on "Y" also got discovered on "all windows workstation collection".
Soon i identified due to bandwidth issue i do not need to manage this child domain "Y"via SCCM. and want to remove these systems from 'All windows workstations' collection on SCCM, as i will be patching "All windows workstations "
every month
I go ahead and removed : AD system discovery >Properties>General tab> Removed the container of the Child domain "Y".
almost one week over. no hopes. systems are still visible.
Some one please help me to get those systems removed ?
Regards
KP

As Torsten said , you may lower the Delete Aged Discovery Data and wait for the task to run or manually delete the clients from SCCM.
Juke Chou
TechNet Community Support

Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
regard is the SCEP client.
I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
Thanks,
-K.R.

Hi,
In R2 there are some new variables you can use to solve this,
http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
-s 120" should do it.
/Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012: clients from SCCM 2007 to 2012: software available instead of installed

Similar Messages

Maybe you are looking for