hi,

i am running a build and capture from the secondary site (on SCCM 2007 R2). Server Locator point is installed on the primary site(sccm 2007 R2). i have given the client install properties as below.

SMSSLP=primary site server fqdn
SMSMP=secondarysite server fqdn

i have set the secondary site boundaries as not protected.

My issue is,

when the build an capture installs software updates started, it hangs on downloading update 1 of xx.

The only error i can find is on the DataTransferService Logs.

it says,

---------

Error sending DAV request. http code 401 status 'unauthorized'

GetDirectoryList_HTTP('http://secondarysiteSERVER.DOMAIN.TLD:80/SMS_DP_SMSPKGE$/XXX00014/bdd178f3-62c9-4431-a645-29d0a7e0affb') failed with code 0x80070005.

----------

Please help.

Hi everyone,

I'm hoping that someone can point me in the right direction on this.  I have a single software package that can only be installed on computers that are getting deployed in one particular branch office.  Is there a way that I can query WMI or some other manner which will allow me to deploy this software during a task sequence deployment, but have the task sequence detect that that the OSD is being done in that particular location? 

The location has a unique subnet so if I could have it detect that the computer is on the 192.168.160.x subnet, it could deploy this software.

Thanks in advance!

Sean

Hi,

We are running SCCM2012. We have some machines and we need to rename those machines during OSD. After booting in winpe, we are asked to select task sequence. As we select task sequence, it just proceed to execute the task sequence. Is there anyway to change the system name during OSD although systems are in Sccm 2012 already with some different name?

Also, any ideas if there are any scripts for sccm 2012 to generate a computer name on serial number or any other convention?

Thanks in anticipation.

Farzan

HI all,

  i am trying to execute hta from OSD TS and i am getting some error. The TS works if i disable HTA (see attached HTA).

Error in TS

I am using x86 winpe bootimage for os x64 bit windows7.

LINK TO SMSTS.LOG https://skydrive.live.com/redir?resid=962001FE4916F0FA!320

THANKS IN ADVANCE

orion

I use the following command on the server running the Multicast Service Point to list the images I have configured to use Multicast (Image properties- Allow this image to be transfered via multicast)

WDSUTIL /Get-AllNamespaces

I also noticed there are registry keys on the Multicast Server that also list the namespace:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Namespaces

I could be wrong but it seems these namespaces are not created until the first client tries to perform a multicast transfer since they don't show up in either the registry or when using the WDSUTIL command after checking the image properties. (Allow this image to be transfered via multicast). Can someone confirm that? I was expecting to see those namespaces created after checking the "Allow this image to be transfered via multicast" box.

The other questions is, I have since unchecked the box "Allow this image to be transfered via multicast" on the image and the image is going out unicast successfully but the registry and WDSUTIL command continue to list the namespace. I guess I was expecting those namespaces to be removed at some point?

Hi,

I am having a rather strange issue with deploying to machines... currently the issue appears to be restricted to imaging Dell OptiPlex 9010 AIO and Dell Vostro 360's.

The OptiPlex 9010 AIO's have an SCCM driver pack direct from Dell... The Vostro 360's do not but I have simply extracted the driver folders and used them like this. I have used the Driver Packages option with a WMI query to target each machine which is working well...

I have created an image using MDT 2012 SP1 and VMware (Windows 7 Enterprise x86 with Windows Updates and applications). The image is then deployed via SCCM task sequence... The apply driver package step runs fine, then the Setup windows and ConfigMgr step runs and then the system reboots.

The problem is that some machines, will sit at installing devices for 3 hours! Then they will reboot and sit at the "Setup will continue after restarting your computer" screen..

My main issue with this is that it is intermittent... e.g. A machine which hangs is rebooted and the OSD sequence is started again it will work fine! I can see in the setupapi.dev.log file the timeframe over which the issue is occurring but I have no idea how to troubleshoot it...

The BIOS's are the latest available from Dell...

Hi

We have SCCM 2007 R3 and we have a couple of BDP is the remote site and I'm planning to implement the OSD

a. May I know if The BDP will support the OSD  ?

b. In case the BDP is working ? .. How do I know if the workstation is getting the data in the BDP that assigned in the said branch ?

c. In which log I can check to troubleshoot (to check where the workstation copying the files ) . Because I'm afraid the if the copying of files is geting from WAN I'll be trouble due to bandwith is not sufficient

Fairly new to USMT, we had a working environment that always advertised the USMT task sequence as an OSD and always ran the advert only once on a machine after converting from XP to Windows7. For some reason a few weeks ago it stopped advertising as an "OSD" which you trigger manually and is now advertising as a mandatory "Program" that wants to run after a few minutes. It does go through the whole process if alowed to run but as soon as the newly build machine is up and running it wants to run the program again. Any idee out there what might have caused this and how to fix?

I'm trying to re-image a new model of PC we are getting from our vendor, OSD starts up OK, and the drive gets partitioned and formatted, but when it tries to proceed on to put the OS on the disk I get a 80004005 error.  When I look in my logs this is what I see:

-------------------------------------------------------

The task sequence execution engine successfully completed the action (Partition Disk 0) in the group (Install Operating System) with exit code 0
Action output: tem32\diskpart.exe" /s "X:\WINDOWS\TEMP\osddiskpart.txt"
Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\osddiskpart.txt"
Process completed with exit code 0
Formatting partitions
Formatting drive C: with NTFS filesystem,method quick
Creating instance of service loader
Loading service
Waiting for service to initialize
Querying for software providers
Found a VDS software provider
Querying for IVdsSwProvider
Querying for packs
Found a VDS pack
Querying for IVdsPack
Querying for volumes
Found a VDS software provider
Querying for IVdsSwProvider
Querying for packs
Found a VDS pack
Querying for IVdsPack
Querying for volumes
Found a VDS volume
Querying for IVdsVolumeMF
Querying for access paths
Found a VDS pack
Querying for IVdsPack
Querying for volumes
Found a VDS volume
Querying for IVdsVolumeMF
Querying for access paths
Found a volume with access path 'C:\'
Querying for IVdsVolume
Querying for IVdsVolumeMF
OSDDiskPart.exe completed successfully.

The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147500037
Action output: "%1" %*
Set command line: "OSDApplyOS.exe" /image:NUH00032,1
Not a data image
ApplyOSRetry:
TSLaunchMode: PXE
OSDUseAlreadyDeployedImage: FALSE
Searching for next available volume:
  Volume C:\ is a valid target.
Found volume C:!sSystemPart.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\diskvolume.cpp,128)
Unable to locate a bootable volume. Attempting to make C:\ bootable.
bBootDiskDefined == true, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,677)
MakeVolumeBootable( pszVolume ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)
ConfigureBootVolume(targetVolume), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,364)
System partition not set
Unable to find the system disk
Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system.
Unspecified error (Error: 80004005; Source: Windows). The operating system reported error 2147500037: Unspecified error

The task sequence execution engine failed execution of a task sequence. The operating system reported error 2147500037: Unspecified error

---------------------------------------------------------------------

I made sure that I had the correct drivers loaded in my boot image for the SATA hard drive.  This is a completely new design that is now using a Core i5 processor with a Intel DQ76SW motherboard.  I tried changing the SATA hard drive to IDE (Compatibility mode), but that did not help.

Any suggestions?

I am looking at a issue with a TS that does not continue after the setup on windows and configmgr step.

The configmgr seems to be in provisioning mode after the restart? As both these values are set to true when logging on and checking the registry.

32bit Windows OS
HKLM\SOFTWARE\Microsoft\CCM\CcmExec!ProvisioningMode

64bit client Windows OS
HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec!ProvisioningMode

SMSTS.log

Successfully complete the action (Restart Computer 1) with the exit win32 code 0 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Sending status message . . . TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
MP server servername.COM and port 80. SSL=false. CRL=false. TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Site code: GBH TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Client machine name: clientname TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Client Identity: GUID:b4b63e85-2c62-4119-9c2d-0eda12806fa9 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Advertisement ID: advertname TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Package ID: packageackage TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Sending StatusMessage TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Formatted header: TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>699EC53C-6AC6-4EB0-81A9-DA424B2B9F2C</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2013-08-21T07:01:06Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2564"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
CLibSMSMessageWinHttpTransport::Send: URL: servername.COM:80  CCM_POST /ccm_system/request TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
The request has succeeded. 200 OK TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Clear local default environment TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Updated security on object C:\_SMSTaskSequence. TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSNextInstructionPointer=184 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=184 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSInstructionStackString=0 182 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a TS execution environment variable _SMSTSInstructionStackString=0 182 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Save the current environment block TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Successfully save execution state and environment to local hard disk TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
OSD type of task sequence. ignore the service window setting TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Reboot to local harddisk TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
_OSDGinaIsConfigured variable set to TRUE TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
_SMSTSServiceStartType variable set to  TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Calling RebootSystem() TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Path variable OSDisk converted from C: to 1B2999DB0000100000000000: TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Updated security on object C:\_SMSTaskSequence. TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSNextInstructionPointer=184 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a TS execution environment variable _SMSTSNextInstructionPointer=184 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a global environment variable _SMSTSInstructionStackString=0 182 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Set a TS execution environment variable _SMSTSInstructionStackString=0 182 TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Save the current environment block TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 21/08/2013 09:01:06 2604 (0x0A2C)
==============================[ OSDSetupHook.exe ]============================== OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Logging successfully initialized to C:\_SMSTaskSequence\Logs OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Executing task sequence OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat". OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created OSDSetupHook 21/08/2013 09:01:21 364 (0x016C)
Saving existing desktop wallpaper settings. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Setting desktop wallpaper. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Debug shell is enabled OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Spawning system message loop thread. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Waiting for system message loop to initialize. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Signaling initialized event. OSDSetupHook 21/08/2013 09:01:22 1564 (0x061C)
Entering system message loop. OSDSetupHook 21/08/2013 09:01:22 1564 (0x061C)
Successfully enabled debug command shell support. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Configuring local administrator account OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Installing SMS client OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Client already installed. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
Moving logs to SMS client directory OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)
LOGGING: Resetting log path. OSDSetupHook 21/08/2013 09:01:22 364 (0x016C)

Any ideas?

Hey everyone,

I'm using a standard client task sequence to deploy Windows 8 to devices.  Recently we received a shipment of two Dell XPS 12's and both my task sequences for Windows 7 and Windows 8 have failed.  It tends to stop at the "Preparing Disk 0 Partitions" step and I've left it going for 24 hours and it didn't move on.  When I look at the partitioning after a reboot I notice that there is a 500MB partition 1 at which point I can clean the partitions using diskpart.  I then reboot the computer and try the task sequence again (launching from MDT 2012 U1 boot flash drive) and it stops at that same point.

The strange thing about this request is that I used this same task sequence back in February with the same OS image and I haven't changed the drivers and it worked for me multiple times back in February on the first XPS 12 we received.  Now I can't get it to work on the newest XPS 12's but it does seem to work on all of our desktops and other laptop devices. 

Has anyone else run into a similar problem?  I've searched the web and some people mention drivers but I can see the hard drive in diskpart when I go to the command line after I boot the laptop with the flash drive.

Thank you!

Hi All,

Apologies I'm quite new to SCCM

We are deploying out Windows 7, to a couple of HP machines.

Prior to this we were using to deploy OS's SCCM as normal. I've been doing some research and checked the logs of the failed TS deploy and it refereed to failed to connected to Share/server with current account. Checked NAA and all was ok with that account as confirmed doing other image deploy. In regards to the original query no IP was received from after it failed and I get a  "Boot mgr failed" error. Looks as if I need drivers for this TS, I've added this to the boot image but then when the boot image is downloaded, it stay on "boot staging" for 10 mins, it then fails to re-boot and then we get a GPT error. Any advice or help would be great!

Do I need to add the driver to the TS, if so will .exe do? and where in the TS does this go?

Thanks for all your help in advance

Can someone help me with this error, I can not seem to add network drivers to my x64 bit image any more and can't work out why it is not allowing me.

   Error: Boot image to update: 
	Microsoft Windows PE (x64)

   Error: Actions to perform: 
	Add ConfigMgr binaries
	Enable Windows PE command line support
	Add drivers

   Success: Drivers that will be included: 
	Realtek RTL8139/810x Family Fast Ethernet NIC
	Realtek PCI GBE Family Controller
	Intel(R) 82567LM-3 Gigabit Network Connection
	Intel(R) 82579LM Gigabit Network Connection
	Intel(R) 82567LM-2 Gigabit Network Connection
	Intel(R) 82579LM Gigabit Network Connection

   Error: Failed to import the following drivers:
	Realtek PCIe GBE Family Controller - Failed to inject a ConfigMgr driver into the mounted WIM file

   Error: The wizard detected the following problems when updating the boot image.
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	Failed to inject a ConfigMgr driver into the mounted WIM file
	The ConfigMgr Provider reported an error.: ConfigMgr Error Object:
	instance of SMS_ExtendedStatus
	{
		Description = "Failed to insert OSD binaries into the WIM file";
		ErrorCode = 2152205056;
		File = "c:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
		Line = 4262;
		ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
		Operation = "ExecMethod";
		ParameterInfo = "SMS_BootImagePackage.PackageID=\"AU100002\"";
		ProviderName = "WinMgmt";
		StatusCode = 2147749889;
	};

Hi all,

we are using a SCCM 2007 R3 infrastructure with multiple Secondary Sites. Active Directory is prepared for storing Bitlocker.

Our Task Sequence works like a charm since 2 years ago. There wasn't ever a Problem with Bitlocker Recovery Password Backup to AD.

Now we started to implement Read Only Domain Controllers (RODC) on several remote sites. As far as I know those RODC work as expected, but I didn't had a look on those.

So when a Client is staged on a remote Location with a RODC on site, the step "Enable Bitlocker" Fails, because the Recovery key can not be stored in the AD. The following error Message appers in the Eventlog:

Experts,

I have a small VB script file to delete folder in c drive and tested manually working fine. When tested in SCCM Task Sequence it wont work. i have tried as batch file also, but no luck. Is there any way to call the script in SCCM Task sequence? how to achieve this task, please advice.

I have a task sequence that fails while downloading the WIM. It starts downloading, gets to a certain percentage then starts over, it does this a couple times before failing with error 80070002.

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 16% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 39% of file C:\_SMSTaskSequence\Packages\PRK00025\ENx64W7.wim

Here's the really strange part, If I F8 and ping the server, it replies and the download continues. The ping is losing packets which I suspect is why the download is failing. I plug into the same port with a working laptop and I don't lose packets. I tried updating the drivers in the Boot WIM to the most current version, older versions, same result. I know it's not Network Access Account since the download starts (and finishes as long as I'm pinging). Any ideas?

Thanks!

Hi Guys,

I have a huge problem. Heres the dp

SCCM 2012 running on Windows Server 2008r2 on ESX with a VMXnet3 10gb Uplink

Autocast

1gb to the client

Im getting 20-30 % client nic usage on a single client autocast when i put 10 on the autocast client nic useage drops to 0.5-2%

On the Server we are seeing next to nothing i think it is 1,500,000bps under resourse monitor

We have all Cisco Gear, We have tried all sorts of settings currently set at

ApBlockSize=1385

TpCacheSize=7550 we have also tried 3145 and it makes no diffence to the speed.

And it takes ages to deploy a 36gb wim file and usual about 40% of the time we get Sparse file encouted when decompressing the wim after file transfur then a hash check failed in the SMSTSlog file

Cisco Guys have looked no issues from their end....

is it the VMXnet / 2008r2 / WDS setting anyone else got these horrible teething issues its so close the the end of the year if i have to go to using ghost to deploy 4500 machines to prevent corruption.. ill go crazy..

Some people are saying this occours with a 2008r2 distrubution point is this true?

I have read all these none of them make any difference

http://support.microsoft.com/kb/2582106?wa=wsignin1.0