Can anyone confirm that  SMSTSPostACTION still works with Configmgr 2012 R2? I know it worked with R1 because I used it all the time

Any command I use in SMSTSPostAction is seemly ignored, it's driving me crazy.

Hi everyone,

I am experiencing some problems regarding running a task sequence for unknown computers.

When I boot certain computers from PXE, I will receive an abortpxe.com

I have verified the following in my environment:

• No duplicate "SMBIOS GUID" in my  environment
• No duplicate "MAC-addresses" in my enviroment
• x64 & x86 unkown computer is located in collection "Unknown Computers"
• Correct TS (with correct boot image) is targetted for this collection

In SMSPXE.log I can find the following:

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: No boot action. Rejected. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: Not serviced. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 7/07/2014 12:37:53 2052 (0x0804)

Item key "2046820***" is the corresponding "x64 Uknown Computer". Sometimes this will be "x86 Unkown Computer" for the same device.

When looking at previous entries in the logfile, this computer was once unkown and wa able to receive a PXE:

3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: device is not in the database. SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820***" ServerName="" ServerRemoteName=""><Machine><ClientID>96de0ff0-0bc2-4f21-ac90-***********</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019" BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Looking for bootImage D3000019 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)

What could be the issue? Is it possible that there is still some record referring to this PC and how can I trace/delete it?

Would restarting the WDS server solve this issue?

Thanks in advance!

Hi everyone,

I wouldl like to have your opinion on maintaining a lifecycle for a PC in SCCM. Mostly for restaging a PC. This is the process which has been implement at the customer for who I work at the moment:

• Run deployment for Unknown computers (PXE) which will export MAC Address + Serialnumber. This is inserted in a DB with all the other information of the asset (This information is scanned by some other employees)
• When we want to stage this asset, we select this PC in our custom tool. This selection will add the computer to SCCM (based on MAC) to the correct collection with a W7 deployment. PXE is used to receive this deployment.
• When this asset returns, we remove computer from SCCM & AD

Afterwards when we want to restage this PC, we will run this entire process again. The idea behind this is that all previous information of this asset in SCCM is deleted.

The previous weeks, I have read about GUIDs, AD discovery and so on and it looks to me that this process isn't the best on the market :) Do you want to share me some information about what would be the best scenario and how we can improve?

Because at the moment, we are facing some issues about reusing these PC's..

• Assets which are still located in SCCM after delete (process is not followed by employees). This will result in PXE erros which need manual fixing.
• Sometimes AD computers aren't deleted and will sync back to SCCM (without MAC address)

Wouldn't it be better to use SMSBIOS GUID rather than MAC since SCCM will target first on this value? Or still not unique since vendors not always create unique GUIDs?

Thanks for the ideas!

Kind regards

Hello All,

Thank you in advance for the help. I am trying to validate a configuration I would like to put in place for a client.

The client has Configuration Manager 2012 set up to manage computers in a non-trusted domain with no MPs in the non-trusted domain. There are DPs in the non-trusted domain. The site runs in an https configuration for these clients. We have configured a subordinate CA in their forest that trusts the CA in the forest that hosts the ConfigMgr site servers and all certs are working fine.

My question: Will OSD function correctly for computers in the non-trusted domain? Or so I need to have an MP in the non-trusted domain as well?

Thanks!

I would like to modify the SCCM boot image so that it runs a script before it loads the Task Sequence list in WinPE.

In WDS, I could just modify the startnet.cmd file to have it do something before it loads the WDS setup.  The SCCM boot image does not appear to use the startnet.cmd file.  Is there another file it uses to call the SCCM application that list the task sequences and sets up the network?  Anyone know what that is so I can have it call a script before it starts that process?

Thank you for your help!

Hello Everybody,

I have been trying for nearly two weeks to get a side by side migration to work for my company's Windows 8.1 refresh project.  We are trying to automate this process, so my thinking is to leverage USMT to capture the data from Vista and create an association in SCCM with the end user's Windows 8.1 box.

Before I start seeing the same feedback that I have seen in similar threads I will clear up a number of issues that people will immediately point out.

1) Vista is not officially supported by SCCM 2012 R2. (The capture step runs fine)

2) Vista needs to run on USMT 4.  I already have 2 separate task sequences calling on different packages.  The Capture runs in USMT4.0 and the restore is running USMT 6.x.x.

My big question is: Is there ANY WAY to specify the State Store Path in the restoration task sequence.  I should think it would inherit that logic from the State Migration Point, but it is looking to some unorthodox path based in the root directory of the SMP's host server.  I tried to use a task sequence variable (OSDStateStorePath EQUALS blah), but it doesn't seem to be applying any functional logic, and is rather checking to see if that value is set in the SMP (which it fails) and continues on anyway.  Since this is not an officially supported migration according to M$, there is no help in the official technet documentation.

Thanks!

Hello,

I am running across a strange problem that is only affecting some machines. We are imaging via OSD task sequence, 2012 R2 and some machines do not register properly with SCCM. When I say not registering, I mean it doesn't get its Site code and missing most of its actions. Most machines that we image work fine, but the odd one doesn't register using the same task sequence that we use on other PC's. When I watch the task sequence steps go through I noticed that right after the installing SCCM client step it boots right into windows. Basically skipping the steps we have set afterwards, the next step is to install some software (adobe reader, SCEP, and a few others).

I also noticed it seems to happen more often with certain model machines. I have an HP Z420 and an HP Folio 9470m. These consistently fail to register everytime I image.

I've tried quite a few fixes I found online, but nothing has worked as of yet. The most recent fix I tried was to delete the hardware inventory and then rebuild it. That did not work. Entering SMSMP= in the Setup Windows and Config manager step also did not work. I also tried entering in our DNS server into the registry under the CCM directory. It appears something is happening during the client install (or not happening). But why only certain machines? Most work fine.

Our fix is to simply re-install the client after imaging, this solution has been working for us but I want to find a more permanent solution.

Any ideas?

Hi guys,

After upgrading to R2 recently our Primary Site Server which hosts a DP will no longer PXE. I believe this due to the WDS service not starting. Other DP's are still functioning correctly.

I have done the following to try and resolve:

• Applied http://support.microsoft.com/kb/2905002/en-us
• Reinstalled wimgapi.msi
• Removed and re-added the DP according to this: http://social.technet.microsoft.com/Forums/en-US/775f96eb-011e-4b91-b9a1-264877a684da/after-upgrade-from-sccm-2012-sp1-cu3-to-sccm-2012-r2-pxe-service-role-crashes-wds-service?forum=configmanagerosd
• Ensure that  Microsoft Visual C++ 2008 Redistributable is installed

The server is a Windows 2012 VM.

Any suggestions for resolving this would be appreciated.

Regards,
Locust12

When booting up a USB thumb drive, during the 'Initializing hardware devices...' stage, the process fails with 'Unable to read task sequence configuration disk'.

I've uploaded the smsts.log to my OneDrive, but here are some relevant snippets:

LOGGING: Finalize process ID set to 708	TSBootShell	7/21/2014 9:39:21 AM	712 (0x02C8)
==============================[ TSBootShell.exe ]==============================	TSBootShell	7/21/2014 9:39:21 AM	712 (0x02C8)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'	TSBootShell	7/21/2014 9:39:21 AM	712 (0x02C8)
Debug shell is enabled	TSBootShell	7/21/2014 9:39:21 AM	712 (0x02C8)
Waiting for PNP initialization...	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,164)	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,120)	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\bootsystem.cpp,112)	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (0)...	TSBootShell	7/21/2014 9:39:21 AM	716 (0x02CC)
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,164)	TSBootShell	7/21/2014 9:39:23 AM	716 (0x02CC)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,120)	TSBootShell	7/21/2014 9:39:23 AM	716 (0x02CC)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\bootsystem.cpp,112)	TSBootShell	7/21/2014 9:39:23 AM	716 (0x02CC)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (1)...	TSBootShell	7/21/2014 9:39:23 AM	716 (0x02CC)
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,164)	TSBootShell	7/21/2014 9:39:25 AM	716 (0x02CC)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,120)	TSBootShell	7/21/2014 9:39:25 AM	716 (0x02CC)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\bootsystem.cpp,112)	TSBootShell	7/21/2014 9:39:25 AM	716 (0x02CC)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (2)...	TSBootShell	7/21/2014 9:39:25 AM	716 (0x02CC)
...
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (27)...	TSBootShell	7/21/2014 9:40:15 AM	716 (0x02CC)
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,164)	TSBootShell	7/21/2014 9:40:17 AM	716 (0x02CC)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,120)	TSBootShell	7/21/2014 9:40:17 AM	716 (0x02CC)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\bootsystem.cpp,112)	TSBootShell	7/21/2014 9:40:17 AM	716 (0x02CC)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (28)...	TSBootShell	7/21/2014 9:40:17 AM	716 (0x02CC)
::GetVolumeNameForVolumeMountPointW( sDevicePath, szDeviceVolumeId, szDeviceVolumeId.size()), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,164)	TSBootShell	7/21/2014 9:40:19 AM	716 (0x02CC)
DevicePath::DeviceNamespaceWin32Path(sDevicePath, rsWin32Path), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\devicepath.cpp,120)	TSBootShell	7/21/2014 9:40:19 AM	716 (0x02CC)
DevicePath::ArcToWin32Path(pszBootPath, rsLogicalPath), HRESULT=80070003 (e:\qfe\nts\sms\framework\tscore\bootsystem.cpp,112)	TSBootShell	7/21/2014 9:40:19 AM	716 (0x02CC)
ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM' (0x80070003). Retrying (29)...	TSBootShell	7/21/2014 9:40:19 AM	716 (0x02CC)
bGotPath, HRESULT=80070003 (e:\qfe\nts\sms\client\tasksequence\bootshell\configpath.cpp,42)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
ConvertBootToLogicalPath failed after retries. Giving up.	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
GetConfigPathFixedDisk(sArcPath, sWinPEFolder), HRESULT=80070003 (e:\qfe\nts\sms\client\tasksequence\bootshell\configpath.cpp,326)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
Failed to find the current TS configuration path	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
ConfigPath::FindConfigPath(sConfigPath), HRESULT=80070003 (e:\qfe\nts\sms\client\tasksequence\bootshell\bootshell.cpp,545)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
Failed to find the configuration path. 
The system cannot find the path specified. (Error: 80070003; Source: Windows)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
Execution failed with error 80070003.	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,809)	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
GetTsRegValue() is unsuccessful. 0x80070002.	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
End program: 	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
Finalizing logging from process 708	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
Finalizing logs to root of first available drive	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)
LOGGING: Setting log directory to "C:\SMSTSLog".	TSBootShell	7/21/2014 9:40:21 AM	716 (0x02CC)

Although this problem seems to be more common on newer hardware (Lenovo M93z, Dell Latitude 7440 & 7240), its also happening on older hardware as well (Dell OptiPlex 780, Latitude 6420).  Even though the thumb drives I'm using are USB 3.0 drives, the OptiPlex 780 do not have USB 3.0 ports.  (The Latitude 6420 I believe does have USB 3.0 ports, but that only represents a very small fraction of our deployment versus the 780 which is something like 20%)

The majority of my thumb drives are Kingston DataTraveler 100 G3's (16gb) which are pretty much all black.  I have a few Kingston DataTraveler 16GB G3 drives, which are white & blue, and they seem to work without issue.

Tests performed thus far with the all-black DataTraveler thumb drives:

• Tried front & rear USB ports
• Tested a known working USB drive (the one that worked on the OptiPlex 755) with the OptiPlex 780 but it didn't work
• Tested the 'faulty' USB drive on another system (OptiPlex 755) and it works fine
• Recreated USB drive, same error
• Totally wiped USB drive: diskpart > lis dis > sel dis 1 > cle > cre par pri > for fs=ntfs quick > ass > exit
• Thought maybe it was the internal disk so I made sure I could browse it, and I can
• Thought maybe it was the internal disk so I totally wiped that as well diskpart > lis dis > sel dis 0 > cle > cre par pri > for fs=ntfs quick > ass > exit

I tried the other USB drives I have

• white & blue Kingston DataTraveler 16GB
• all-black Kingston DataTraveler 111 16GB
• 2x no-name vendor issued (free) drives

And they all work swimmingly on that OptiPlex 780, the Latitude 6420 and the other new hardware here.

I don't want to beat a dead horse here, but I want to make sure I'm not going crazy, and not overlooking something simple.  Short of ordering more USB drives, is there anything else I can try to be sure I've been a thorough as possible?

Resources:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/8f10dde4-5a72-4c0c-a811-bda429f3d782/unable-to-read-task-sequence-configuration-disk?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/a60feb9b-d968-4a2c-9449-773c61bcdf58/os-deployment-unable-to-read-task-sequence-wpeinitexe-does-not-start-automatically?forum=configmgrosd
http://social.technet.microsoft.com/Forums/en-US/8f10dde4-5a72-4c0c-a811-bda429f3d782/unable-to-read-task-sequence-configuration-disk?forum=configmgrosd
http://social.technet.microsoft.com/Forums/en-US/fc664af4-88ad-45c8-904a-b23a3bf4fe56/unable-to-read-task-sequence-configuration-disk?forum=configmgrosd
http://social.technet.microsoft.com/Forums/en-US/fc8865f1-5d9d-44d5-889c-773bcf6623b4/unable-to-read-task-sequence-configuration-disk-sandisk-cruzer-4gb?forum=configmgrosd
http://social.technet.microsoft.com/Forums/en-US/8304ac80-0d0b-442a-aa1e-390e19b7e58b/unable-to-read-task-sequence-configuration-disk-winpe-and-intel-82566dm-nic-driver?forum=configmgrosd
Among others...

SCCM 2012 Task sequence.  OS and drivers install fine, the machine
joins the domain.  Most of the applications install fine, and looking at
the status messages, they all install.  However, when the task sequece
completes, and you log into the machine, several apps (always the same
ones, like the Microsoft Primary InterOP files) do NOT show in "Add -
Remove Programs".  Running the install program after the fact it does
then show up there. 

Since no errors are reported,i am not sure how to troubleshoot this one.  Any ideas?

Greetings,

  I have a build and capture task sequence. In the Winpe phase I create one single partition (no bde). During the WinPE phase, diskpart says this drive is C and I can copy stuff to the C drive no problem. Once the "Setup Windows and configmgr" step starts and reboots into the OS, the OS in "my computer" says its on the D drive. How can I make sure that the reboot into the OS keeps the C drive for the boot partition?

Thanks

David Z

Hi All,

I am in the process of creating an golden Image for Windows 7 SP1 x64 using SCCM 2012R2, installed on Windows Server 2012R2.

To create an image I created a build and Capture TS from scratch using default settings.

The build VM is not joined to the domain, I added the SMSMP = fqdn and DNSSuffix=fqdn to the client settings.

The process goes well until the VM is being captured, It start with scanning and capturing volume 1, which is ok.

Then the process starts scanning Volume 2 (Windows volume) then the VM reboots. The logs do not reveal anything, they go only up until the system reboots after sysprep. After the failed capture, a WIM file is created of 7 MB size.

I read on another forum that the workaround for this is to shutdown the VM after Sysprep phase and then power it up again. That works for me too. Now the VM image is captured properly.

When I use the same TS on a Laptop, the TS finishes correctly, capturing the installation. Dont have to shut it down.

Any ideas what could be wrong here?

Some additional info:

Hyper-V 2012R2 hosts are patched.

The VM in use is Gen-1 with a legacy nic.

AV on the SCCM server is shutdown for testing.

Share permissions for WIM location are ok and accessible for Build and Capture client (used F8 to check)

DHCP settings and DNS are ok, the client get's proper IP and can resolve SCCM MP and shares.

Hi,

I am trying to deploy Windows 7 via an OSD task sequence. I am deploying the SCCM 2012 SP1 CU3 client in the task sequence - with the "Setup Windows and ConfigMgr" step.
The behaviour I am noticing is that this steps causes a machine reboot during that step and the SCCM client then takes a little while to re-initialize.
We are trying to optimize this OSD sequence to make make it go faster.

So here are my questions:

1. Is this normal behaviour the this still will cause a reboot? (I have looked through the logs and cannot see a clrear reason why it is doing it).

2. Is there any way I can suppress it. (I am not seeing any properties to do so) ?

3. In case I have missed it is there a clear log that would indicate 'why' it would be rebooting?

Thanks,

Ward

Hi Friends,

DELL M3800, M4800 etc models are capable of RAID, and by default the SATA Options in bios is : RAID ON, is there a script or command line which will change it to AHCI

i would like to add this command line/script in the Task sequence for operating system deployment, so that even though the tech forgets to change the bios settings the command line/script will make the change before installing the OS

Best Regards,,

Tanoj

OSLM ENGINEER - SCCM 2007 & 2012

I have a few secondary sites that appear to have content that should be removed to clear up space within the Distribution Point.  I have examined the Content library explorer within the SCCM Toolkit; however, I am not discovering a good way to find and remove old content. 

I have read Microsoft’s http://blogs.technet.com/b/configmgrteam/archive/2013/10/29/understanding-the-configuration-manager-content-library.aspx explanation on orphaned content and am wondering the ‘best” way to remove content on the DP.

Any tips on cleanup would be helpful.

Thank you

Hi,

I am dealing with a strange issue with a State Migration Point installed on a server also having DP and Out of Band Service Point roles.

The SMP is working fine when using USMT in Task Sequences to store and retrieve data in a Refresh scenario, but state store information is not transferred to the site server. This results in the User State Migration node being empty in the ConfigMgr console, so I cannot see the progress nor the store path for each migration performed with the SMP.

My first action was to uninstall the SMP role, reboot the server and reinstall the role. The smpMSI.log file gave me a return code 0 for removing and reinstalling the role, but the issue is still present.

I noticed 2 strange things on the SMP server:

• SVF files are accumulating at the root of the SMS folder, shouldn't they be in a Outbox folder? Those files contain information related to the SMP. The registry valuesStateMsgDir and StatusMsgDir under HKLM\Software\Microsoft\SMS\SMP\StateStore are set to E:\SMS. It doesn't sound right.
• In the smpisapi.log file, every 5 minutes, it tries to create a folder for a USMT store, the problem is that no Task Sequence is currently running, the same folder is tried again and again, without being created on the SMP store. If I run a TS to capture data with USMT, I see another folder being created successfully on the SMP Store for that one. Here is a sample of the log file for the folder always retried, it seems to me that an orphan entry somewhere is causing this loop:
  
  <![LOG[SMPStoreMgr worker thread signaled]LOG]!><time="07:44:43.929+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="616" file="smpstoremgr.cpp:932">
  <![LOG[========== BEGIN: HttpExtensionProc ==========]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="0" thread="3444" file="smpisapi.cpp:404">
  <![LOG[Query string to parse: 'op=healthcheck'.]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="3444" file="smpisapi.cpp:139">
  <![LOG[Creating state store - E:\USMT\SMPSTOREE_FB2185F2$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="3444" file="smprequesthandler.cpp:1408">
  <![LOG[Creating Migration Status Parent Directory - E:\USMT\SMPSTOREE_FB2185F2$\MigrationStatus.]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="3444" file="smprequesthandler.cpp:1482">
  <![LOG[Statestore - E:\USMT\SMPSTOREE_FB2185F2$\MigrationStatus exists.]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="2" thread="3444" file="smprequesthandler.cpp:1494">
  <![LOG[Creating Migration Status Child Directory - E:\USMT\SMPSTOREE_FB2185F2$\MigrationStatus\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473.]LOG]!><time="07:44:51.775+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="3444" file="smprequesthandler.cpp:1512">
  <![LOG[Returning status "200 OK"]LOG]!><time="07:44:51.806+240" date="07-22-2014" component="smpisapi" context="" type="1" thread="3444" file="smpisapi.cpp:230">
  <![LOG[========== END: HttpExtensionProc ==========]LOG]!><time="07:44:51.806+240" date="07-22-2014" component="smpisapi" context="" type="0" thread="3444" file="smpisapi.cpp:482">

The smpmgr.log file doesn't show up any error.

Any help will be appreciated!

Tnx

Patrick

Hi all,

This issue is already resolved, so I thought I'd just write about my experience in case it helps someone else.

We recently upgraded from Configuration Manager 2012 SP1 CU3 to Configuration Manager 2012 R2 CU1 and immediately began having problems with OS deployment. Most of the problems were easy to fix (like needing to update our MDT boot images and change our task sequences so that they use the R2 client instead of the SP1 client), but one issue was very difficult to identify and resolve.

We have a lot of Lenovo W540 and Dell Precision M4700 laptops. We are using the latest official driver packs from Lenovo and Dell for these models, and everything worked fine while we were on SP1 CU3. After upgrading to R2, these two models started failing OS deployment. The symptoms varied, but typically included a corrupt Segoe UI font:

We would also see these errors while setting up the Configuration Manager client during the task sequence:

"This application requires one of the following versions of the .NET Framework: v4.0.30319 Do you want to install this .NET Framework version now?"

So since this was only occuring on two specific models, I assumed it was driver related (even though the exact same drivers had worked in SP1). I initially disabled the steps that install drivers for the W540 and M4700 and just added a step to install their network drivers. Without the machine-specific drivers loaded, OSD worked, but I had to manually load drivers after it finished, which was not ideal. I concluded there must be some sort of conflict with something new in the R2 CU1 client and one of the drivers, but narrowing down which driver was causing the problem was too time consuming, so I gave up on it.

I tried using a base OS image that was not built using Configuration Manager, so it wouldn't have any version of the CM client in it. This worked fine, even with all the drivers enabled. I also tried using one of my old base OS images that had the SP1 CU3 client in it, and this also worked. So that made me suspect the 2012 R2 CU1 client was to blame for sure.

I finally tried re-building my base OS images using the 2012 R2 client, but without CU1 (I just removed the PATCH= argument from the "Setup Windows and ConfigMgr" step and re-ran the build and capture task sequence). This worked fine, and is the solution I'm settling on. I can still include the PATCH= argument when I deploy this newly-captured base image.

I don't know the full root cause, but it appears to be some sort of conflict with the device drivers used by these two specific models and something included in CU1. I suspect one of the drivers tries to upgrade .NET framework while a reboot is in progress, or something like that, but that's as far as I got.

I hope this helps someone else, or if you have any ideas on what's broken, I'd love to hear about it.

--Russel Riley

PXE booting is working fine with all other Dell models. PE environment loads, OSD password prompt is displayed. Task sequences are displayed.

With just this model, Dell Latitude e6440, it gets to the point where we should be prompted for a password, hangs and then reboots. When I hit F8 and enter ipconfig it shows no ip address If I do ipconfig /renew i get "The operation failed as no adaptor is in the state permissible for this operation." If I boot the computer into Windows (OOBE as shipped by Dell) it gets an IP successfully. I've updated our WinPE boot image with every network driver I can find from Dell for this model. Any other suggestions? We are booting with a x86 WinPE wim file.