VacTacks11

Hi folks, Have a customer that's looking to do USMT to a UNC path in a Replace Scenario. The drawback of course is that we can't use the State Migration Point, so Requesting/Releasing the Mig file is out; nor can we use a %ComputerName% variable, given the new computer name. Any ideas on how to accomplish this? Thanks

Hi. Is it possible to have user data backed up to the DP that serves the image? I'm working with a client who has MDT integrated with their 2012 environment, and in a Refresh scenario, they want their user data backed up to a State Migration Point located on the DP that served the image. From http://technet.microsoft.com/en-us/library/gg712679.aspx#BKMK_BoundarySiteAssignment, "You can associate one or more distribution points and one or more state migration points with each boundary group. You can also associate a distribution point or state migration point with multiple boundary groups." would seem to be the correct solution, but I'd like to verify with the braintrust that this is the correct method. Thanks

Hey guys, Was wondering if any of you have any experience with creating Provisioning Windows To Go using ConfigMgr 2012? The step that I'm flaking on is under creating Prestaged Media (http://technet.microsoft.com/en-us/library/jj651035.aspx#BKMK_CreatePrestagedMedia), specifically #15 where it says to create Prestart commands. I've never created a Prestart command, and the documentation doesn't show how to create the command. Tells me WHAT commands to create, but not HOW to. Thanks

That was it. It was the Build & Capture I created from the VM that caused this. I created a new VM using the Client in my domain and sure enough, it's working now. Thanks again for all your help. Really.

1) Just want to say thanks for your help so far. It's appreciated. 2) I didn't have the SMSMP in the TS Client install properties, as it wasn't in the TS Client install properties for the SCCM 2007 MDT Task Sequence. Didn't think I would need it here either. But I have entered it there now. 3) I built and captured a VM for my W7 machine, but I used VLK media to do so, and the messages I kept seeing in smsts.log indicated that I shouldn't have used a license key when I captured that image. While I doubt that would have anything to do with this, since I'm out of ideas here... I'll write back when I've captured a new machine. See what happens there.

You know, looking back on it now, it seems like such an easy thing, but, yeah, the ConfigMgr package created by default didn't have a Program associated with it. I created a Program from Definition. That being said, it still didn't work for me. I'm not quite sure where to look now. It finds the MP now, which is stellar, but after the TS configures ConfigMgr, it boots into Windows without officially completing anything. I think I may have to recreate the Build & Capture Windows 7 image. I see a ton of Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type errors in the smsts.log file, which I've been able to ascertain is having used a license key in a VLK capture (something you're not supposed to do I guess). Really just grasping at straws here.

My bad. Yes, they all show as having ADX as the Site Code. I just talked to the networking guys about how there are some IP Subnets (including the one I'm testing on) that are not present in AD. I found that as I was searching through my locationservices.log file and it wasn't able to retrieve AD site membership. Now to see where your suggestion takes me. Thanks again

I did not do that, actually. Wasn't aware that that's a step that should be done. Is that recommended?

Recreating the task sequence didn't help at all, so I entered SMSMP=[sERVER] FSP=[sERVER] in the Setup Windows and ConfigMgr task step. Didn't help either. Now I'm onto disabling the Firewall - maybe I didn't enable a port or something.

That DecryptStringWithPwd failed line got me wondering if the ConfigMgr-Push account (the account we use to install the Client) had the wrong password entered. Sure enough, when I went into Client Push and clicked Verify, it said the password wasn't correct (even though it was correct when I originally set it up). Reset the password, verified it, and now the smsts.log is virtually empty. There's really no entry that stands out, other than maybe Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE (which it was). Restoring SMS client identity The client certificates were not found in the environment. New certificates will be generated I'm going to recreate the MDT OSD Task Sequence and see if that helps at all.

We have a few pilot users that have the client installed, yes, and the ADX site code shows during Client Push. I updated the Boundary Groups to include the IP Address ranges, and I'm now getting ccmsetup.log MSI properties: INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="ADX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" A Fallback status Point has not been specified. Message with STATEID='00' will not be sent No MPs were specified from commandline or the mobileclient.tcf Retrieving client operational settings from AD ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ADX))' An MP does not exist on this machine MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=mous INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="ADX" CCMHTTPPORT="80" CCMHTTPSPORT="443" It looks to me that updating the Boundary Group at least allowed the client to find the MP, but it's still not using said code during install. smsts.log shows DecryptBuffer failed DecryptStringWithPwd failed. 80070057 (a NUMBER of times) Task Sequence Manager could not initialize Task Sequence Environment. code 80004005 Task sequence execution failed with error code 80004005 Non fatal error 0x80004005 in sending task sequence execution status to MP smsts.log seems pretty lit up with red and yellow lines.

Hey guys! Running ConfigMgr 2012 on Server 2012, and trying to deploy a MDT 2012 R1 Windows 7 OSD Task Sequence. The Task Sequence runs to Post Install > Setup Windows and ConfigMgr but doesn't run anything after. I have Restart Computer, Set Status 4, Install Standard Software, and Install Software Updates as tasks to run after Setup Windows and ConfigMgr. The hardware specific driver package installs just fine, and the computer is added to the domain. With the exception of this problem, the OSD Task Sequence works great. ConfigMgr does install, but it doesn't install with a Site Code. smsts-20121217-113749.log shows Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0 MP server http://[servername]. Ports 80,443, CRL=false Setting the authenticator CLibSMSMessageWinHttpTransport::Send: URL: [server Name]:80 CCM_POST /ccm_system/request Request was successful ccmsetup.log shows Failed to get site version from AD with error 0x80004005 SiteCode: PR1 (guessing that's the default one) No MPs were specified from commandline or the mobileclient.tcf A Fallback Status Point has not been specified. Message with STATEID='400' will not be sent As far as Boundaries go, the single DP is in a Boundary Group, but this morning AD Discovery had really only found IP Subnets, and not IP Address Ranges (e.g. it had found IP Subnet 10.11.161.0, but the IP Address Range 10.11.161.1-254 wasn't listed - I've since made that change). I have the Boundary Group set to Allow fallback source location for content. I'm not sure how long it would take for ConfigMgr 2012 to register the new Boundary, but maybe I tried to run the OSD Task Sequence before it had a chance to update AD? The AD schema has been previously extended (this is a migration from SCCM 2007 to 2012), and the 2012 computer account has full permission to the System Management container. In fact, Active Directory Forests [Publshing Status] tab shows as Succeeded as of 10:29 AM this morning. Client Push Installation Properties (2012 client hasn't been pushed out yet...we're still testing OSD) has SMSSITECODE=ADX, which is what the MP is. The OSD Task Sequence has the Installation properties area, but of course when you try to type SMSSITECODE= it flags it and says you can't inject that code in there. This is about where I'm stuck. Would appreciate any help here. Thanks