Search the Community

I running a small SCCM2012R2 Lab in vmware workstation 11 I could fine capture Windows 7 32bit and 64bit But when i try to capture Windows XP Pro SP3 i get following error: What to do from here?? My Mission is to simulate a XP to Windows 7 Migration but first I need to be able to Capture Windows XP so i can deploy XP machines Hope someone here could help me further with my lab test

Hello everyone, I’m having issues with workgroup computers, not domain systems when I request a certificate. The domain computers are receiving their certificates via GPO. It’s extremely weird. It has something to do with Windows 7 and Windows 2008 machines. On a 2003 server, I can request a certificate manually with certutil and "see" the certificate template. I copy over the exact command on windows 7 and it can’t "see" the certificate template. The Error --- Template not found. I have the following configuration: CA Enterprise I have created the SCCM Client Certificate I have created the SCCM Web Server Certificate I have created the SCCM Distribution Point Certificate GPO is configured SCCM 2012 R2 CU2 configured to do HTTP and HTTPS Installed SCCM Client Certificate Installed SCCM Web Server Certificate Installed Distribution Point Certificate Deployed to a domain computer good on PKI Workgroup Computers: I’m having issues with deploying certificates Windows 7 – (ERROR) not successful Windows Server 2008 R2 – (ERROR) not successful Windows Server 2003 - successful Windows XP – successful How I’m getting the certs for the clients is by utilizing the following scripts from this URL. http://www.ithierarchy.com/ITH/node/48 I did find a couple of errors in the code, but if it’s working on my Server 2003, then it should work on the others. Windows 7 and Windows 2008 R2 seem to have the same issue. The error I’m getting is the following: Command line requesting the cert ---- CertReq –new –f testcomputer.home.pvt.inf c:\client\testcomputer.home.pvt.req Error --- Template not found. SCCMClientCertificate (this is my template)

We have been using USMT for many years kicking off a command line script on each the old and new computer. (Scantate & loadstate). In most cases we use MDT just for the build on a hardware refresh. This allows us to prebuild 100's of laptops and have them on hand when someone has time to swap out. My question is could I use USMT to backup the old computer and then restore it to the new one directly? Basically a "computer to computer" data and settings swap. I thought years ago I read that this could be done. But all of the searches I have done recently come up with nothing. This method would cut down on server space that is needed and cut down on time of backing up then restoring separately. If anyone has information on please let me know. Thanks, Darren

Hello! First time poster and also new to SCCM (2012) in general, but catching on pretty quickly. Much thanks to this forum. A little back story - we created capture media so that we could capture a manually built reference machine (a virtual machine). This capture spit out what would be our new base WIM. It worked great. This base WIM is essentially Windows 7x64 Enterprise SP1, all up-to-date software updates, MS Office 2010, and Internet Explorer 10 only. We kept our base very simple. The issue - We are running in to a very strange problem where we add our base WIM to our deployment task sequence, all seems great until you log in with a domain account. The Windows theme is some sort of "Windows Classic" or "Windows XP" theme. This does not happen for the local admin account though. So, you can log in as local admin, you get Windows 7 Aero theme. Log off, log in as a domain user and you get "Windows Classic/XP" theme (I've tried 4 domain user accounts to rule out the possibility of it being tied to a specific account). Log off and log back on as local admin and you get the Windows 7 Aero again. No idea what could be causing this. I thought it was possibly group policy because I was using a domain user account and maybe something was tied to it, but then I figured this would most likely happen to a lot of users in production and it isn't. I asked a friend and he said maybe look in to the unattend.xml, but I don't really know where to start with that. What could be in there that would be kicking off that classic theme look? This is especially weird when I am using a base WIM that I created from a Win7x64 Enterprise virtual machine that did have Aero turned on when it was captured. I found the following article from TechNet, but this talks about when migrating from XP to Win7. We are going from Win7 to Win7...We are simply updating our Win7 image because our most recent version was created with poor practice. The base WIM has so many programs that not all users need installed on - essentially a fat image and it's no good. The article seemed very close to what my issue is, but I cannot undererstand it. I do not know what scanstate and loadstate are, nor a config.xml. Plus, since I am not coming from XP this probably won't fix my issue. http://blogs.technet.com/b/askds/archive/2010/02/24/get-shiny-with-usmt-turning-the-aero-theme-on-during-xp-to-windows-7-migration.aspx Any help is greatly appreciated. Thank you!

I've recently been playing with maintenance windows and for some reason, the xp test machines don't always pick up the maintenance window and apply it. so as soon as updates are done it just reboots instead of waiting for the window. What am I missing? Thanks, Chad

Here's one for you. I have some Windows XP PC's that dual boot between two partitions. One is commonly used and the other not. The countdown to select the more commonly used partition ( default ) sits at 999seconds. Like using the right click tools on a collection in sccm 2012, does anybody know of a way I could WOL then wait 20 seconds and send a signal 'return' key to select the default partition and start booting. Any help would be greatly appreciated. W

Hi, We are migrating machines from Windows XP to Windows 7 using USMT 5.0 and hardlink. The only thing I have left to do is to include empty folders. Can anyone provide a bit of info on this? USMT seems to ignore them. I have been searching quite a bit and cannot find an answer. Thanks, 1nternetz

I am having a difficult time trying to get the client installed on XP machines that have an older client on them. I know I am overlooking something, I just can't seem to see it. I am running SCCM 2012 SP1 Here is some detailed information from one of the client machines Windows XP SP3 (it did have the SCCM 2007 client installed and was pointing to a different site that was no longer in use) This is the info I have after SCCM 2012 deployed the new clients Shows the Version as: 5.00.7804.100 Client cert: None Connection Type: Unknown Site Code is empty Network is empty Actions only has: Machine Policy Retrieval & Evaluation Cycle User Policy Retrieval & Evaluation Cycle I even tried to manually install the client with: "\\zeus.gwusd.org\SMS_Z01\Client\ccmsetup.exe" /mp:Zeus.gwusd.org SMSSITECODE=Z01 SMSSLP=Zeus.gwusd.org SMSMP=Zeus.gwusd.org DISABLECACHEOPT=TRUE DISABLESITEOPT=TRUE Ccmsetup.exe ran for 30 minutes, but the settings were the same. I attached both the ccmsetup.log and the client.msi.log Thanks! ccmsetup.log client.msi.log

Hello everyone, Here is my situation. I have a Windows XP in DOM A and SCCM A on which I am advertising a task sequence to deploy W7 and join DOM B with SCCM B. The migration/deployment scenario works great, no problem on that. My first steps that are done online (not in WinPE) are the following on the XP machine: -Backup of user settings with USMT -Backup of user data with Robocopy -Change the name of the computer locally/AD with a vbscript that also set the OSDComputerName variable with the new value -Restart on Windows (to validate the renaming) -Restart in WinPE and go on with the classic deployment (Format, dl of the .wim ...) The thing is that everytime, once the machine is in the new AD and SCCM it still has its old computername. Even though the script changed successfully the name of the computer in the AD and locally of the XP. So I am wondering if this is possible to set the OSDComputerName out of WinPE? And if yes am I doing it right? Here is the part of my script where I set the variable: dim env SET env = CreateObject("Microsoft.SMS.TSEnvironment") env("OSDComputerName") = NewComputerName Where the variable NewComputerName is a variable set before with the new computer name (and it works as it changes the value in the AD). The script is run with an account that as domain admin privileges in DOM A and full access on a DFS in DOM B where the script and a csv file containing all the new values are stored. So, what is wrong?? THank you a lot, I have been trying to fix this for days !!

Hello, I have some questions about USMT and config.xml i was hoping someone can help me out. My understanding of using a Config.xml file is that I need one for systems going from XP to Windows 7 and another one for Windows 7 to Windows 7 since the DlManifests are different on the two OS's. So if I run Scanstate.exe on a XP machine, using ConfigXP.xml after upgrading the OS to Windows 7 i have to run the LoadState.exe using the ConfigXP.xml file? And the same goes for Windows 7 reimages. I use ScanState.exe with the ConfigW7.xml and restore using LoadState.exe with the ConfigW7.xml. If the above is true, what is the best way to automate if ScanState.exe was ran from a XP machine, to use the correct Config.XML file once the machine is upgraded to Windows 7? Thank you.

Hi everyone, We currently have over 1000 objects in AD which should all have a healthy SCCM client, but due to the PC's not being turned on all the time the client becomes corrupt for some reason. I beleive the most efficient way to fix those PC's on the network that have SCCM issues is to have a script read from a computers.txt list, which contains all the corrupted computers, and have the script grab that name from the computers.txt list and let the script run a ccmsetup.exe on that remote PC using PSEXEC. We currently use site code AP0 and have the ccmsetup.exe file. ANY SUGGESTIONS WOULD BE GREATLY APPRECIATED.