Quantcast
Channel: Configuration Manager 2007 Operating System Deployment forum
Viewing all 1063 articles
Browse latest View live

OSD - staging boot image fails (80070020) c:\boot already in use

$
0
0

Dear all,

Our OSD fails when initiated within Windows. After doing a couple of tasks like USMT the task sequence, the task sequence reaches the "Restart to Windows PE" step (Restart Computer - The boot image assigned to this task sequence) and fails the step with error 0x80070020 (file in use).


The USMT log looks like this:

Copying boot image locally...	TSManager	01-09-2014 09:51:54	904 (0x0388)
Opening image file C:\_SMSTaskSequence\WinPE\sources\boot.wim	TSManager	01-09-2014 09:51:57	904 (0x0388)
Applying image 1 to volume C:\_SMSTaskSequence\WinPE	TSManager	01-09-2014 09:51:57	904 (0x0388)
Closing image file C:\_SMSTaskSequence\WinPE\sources\boot.wim	TSManager	01-09-2014 09:51:58	904 (0x0388)
Capturing WinPE bootstrap settings	TSManager	01-09-2014 09:51:58	904 (0x0388)
Environment scope "Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}" successfully created	TSManager	01-09-2014 09:51:58	904 (0x0388)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}	TSManager	01-09-2014 09:51:58	904 (0x0388)
==============================[ OSDNetSettings.exe ]===========================	OSDNetSettings	01-09-2014 09:51:58	628 (0x0274)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}	OSDNetSettings	01-09-2014 09:51:58	628 (0x0274)
Captured settings for adapter 1	OSDNetSettings	01-09-2014 09:52:00	628 (0x0274)
OSDNetSettings finished: 0x00000000	OSDNetSettings	01-09-2014 09:52:00	628 (0x0274)
Process completed with exit code 0	TSManager	01-09-2014 09:52:00	904 (0x0388)
Installing boot image to hard drive	TSManager	01-09-2014 09:52:00	904 (0x0388)
Failed to open C:\boot for backup. 
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)	TSManager	01-09-2014 09:52:04	904 (0x0388)
Failed to install boot image. 
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)	TSManager	01-09-2014 09:52:04	904 (0x0388)
Failed to install boot image SC000437. 
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)	TSManager	01-09-2014 09:52:04	904 (0x0388)
Failed to reboot the system. Error 0x(80070020)	TSManager	01-09-2014 09:52:04	904 (0x0388)
Failed to initialize a system reboot. 
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)	TSManager	01-09-2014 09:52:04	904 (0x0388)
Fatal error is returned in check for reboot request of the action (Restart to Windows PE). 
The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows)	TSManager	01-09-2014 09:52:04	904 (0x0388)
An error (0x80070020) is encountered in execution of the task sequence	TSManager	01-09-2014 09:52:04	904 (0x0388)
Sending status message . . .	TSManager	01-09-2014 09:52:04	904 (0x0388)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError	TSManager	01-09-2014 09:52:04	904 (0x0388)
Formatted header:	TSManager	01-09-2014 09:52:04	904 (0x0388)<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:15d9f1d0-fd5a-4db2-9e38-4fa2692741ae</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-01T07:52:04Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="2114"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
	TSManager	01-09-2014 09:52:04	904 (0x0388)
Task Sequence Engine failed! Code: 80070020	TSManager	01-09-2014 09:55:42	904 (0x0388)
****************************************************************************	TSManager	01-09-2014 09:55:42	904 (0x0388)
Task sequence execution failed with error code 80070020	TSManager	01-09-2014 09:55:42	904 (0x0388)
Cleaning Up. Removing Authenticator	TSManager	01-09-2014 09:55:42	904 (0x0388)
Cleaning up task sequence folder	TSManager	01-09-2014 09:55:42	904 (0x0388)
Successfully unregistered Task Sequencing Environment COM Interface.	TSManager	01-09-2014 09:55:42	904 (0x0388)
Executing command line: "C:\Windows\system32\CCM\TsProgressUI.exe" /Unregister	TSManager	01-09-2014 09:55:42	904 (0x0388)

"Failed to open C:\boot for backup" and "Failed to install boot image" because of file in use. I have never seen that before.

I thought it had something to do with the boot image, so I re-built the boot image from an earlier version (injecting the newer drivers etc.) and it worked. For a short period of time I could it would be able to reboot to WinPE with the new boot image. However - now i fails again with the same error, eventhough it's a new boot image and new package - distributed to all DPs etc.

So I think the error is sporadic since I was able to get it to work shortly, or maybe "something" happens to the boot image after a while. But I am at a loss! I don't know how to troubleshoot any further.

Addition details: All the TS's and boot images are created on a parent server, then synced to a child site where everything the TS is run. The parent site had to have WAIK reparied recently (I found out I couldn't create boot images when I wanted to test another boot image, which led to the WAIK repair which fixed the issue about not being able to create new boot images).

Have anybody ever seen this issue before (my google-fu says no)? What to do from here?


In advance: Sorry...


Boot from Media and static IP script

$
0
0

I thought I would give back a bit to the community.  My current engagement has a client where 2/3 of the computers are not on DHCP, and probably won't be anytime soon.  There is a feature deficiency in the SCCM boot from media function, it lets you set the IP address in the initial WinPE startup, but that address isn't communicated to Windows.  Windows comes up expecting to find DHCP.  Hint, hint here anyone from the product group, this should be added to the Apply Network Settings task :)

This script needs to be put in the task sequence right before the Apply Network Settings task sequence step.  The script will check to see if the variables were already set in Windows (which works correctly).  If not (only happens when you are doing a new install) it will read the entries from WinPE and write them to the TS variables needed by Apply Network Settings. 

There is a limitation to the scipt that it can only put in as much as can be entered by WinPE.  So things like multiple DNS servers for example can't be entered into PE, so they can't be transfered to Windows.

Set objWMIService = GetObject ("winmgmts:\\.\root\cimv2")
WQL = "Select * from Win32_NetworkAdapterConfiguration where IPEnabled = TRUE"
Set colNetAdapters = objWMIService.ExecQuery (WQL)

WScript.Echo "Number of adapters is " & colNetAdapters.Count

set objSCCM = CreateObject("Microsoft.SMS.TSEnvironment")

if objSCCM("OSDAdapter0IPAddressList") = "" then

 For Each objNetAdapter In colNetAdapters
  if objNetAdapter.DHCPEnabled then
   WScript.Echo "DHCP Enabled"
  else
   WScript.Echo "DHCP Disabled"
   objSCCM("OSDAdapter0EnableDHCP") = false
   
   if Not IsNull (objNetAdapter.IPAddress) then
    strIPAddress = objNetAdapter.IPAddress(0)
    WScript.Echo "IP Address:       " & strIPAddress
    objSCCM("OSDAdapter0IPAddressList") = strIPAddress
   end if
     
   if Not IsNull (objNetAdapter.IPSubnet) then
    strIPSubnet = objNetAdapter.IPSubnet(0)
    WScript.Echo "IP Subnet:        " & strIPSubnet
    objSCCM("OSDAdapter0SubnetMask") = strIPSubnet
   end if
     
   if Not IsNull (objNetAdapter.DefaultIPGateway) then
    strIPGateway = objNetAdapter.DefaultIPGateway(0)
    WScript.Echo "IP Gateway:       " & strIPGateway
    objSCCM("OSDAdapter0Gateways") = strIPGateway
   end if
     
   if Not IsNull (objNetAdapter.DNSServerSearchOrder) then
    strDNSServerSearchOrder = objNetAdapter.DNSServerSearchOrder(0)
    WScript.Echo "DNS Server:       " & strDNSServerSearchOrder
    objSCCM("OSDAdapter0DNSServerList") = strDNSServerSearchOrder
   end if

   if Not IsNull (objNetAdapter.MACAddress) then
    strMACAddress = objNetAdapter.MACAddress(0)
    WScript.Echo "MAC Address:      " & strMACAddress
   end if
     
   if Not IsNull (objNetAdapter.DNSDomainSuffixSearchOrder) then
    strDNSDomainSuffixSearchOrder = objNetAdapter.DNSDomainSuffixSearchOrder(0)
    WScript.Echo "DNS DOMAIN:       " & strDNSDomainSuffixSearchOrder
   end if
   
   if Not IsNull (objNetAdapter.WINSPrimaryServer) then
    strWins = objNetAdapter.WINSPrimaryServer
    objSCCM("OSDAdapter0EnableWINS") = true
    if Not IsNull (objNetAdapter.WINSSecondaryServer) then
     strWins = strWins & "," & objNetAdapter.WINSSecondaryServer
    end if
    WSCript.Echo "WINS Server:      " & strWins
    objSCCM("OSDAdapter0WINSServerList") = strWins
   else
    objSCCM("OSDAdapter0EnableWINS") = false
   end if

   objSCCM("OSDAdapterCount") = 1
      
  end if
 Next
End If


Bob

Clients to find from a server

$
0
0

Hi  ,

is it possible to find out , how many clients got installed osd form a particular sever.

eg: if we have a server like ABCD001 with PXE enabled , how to know how many clients got installed OS from that server.

Thanks in Advance.

br

kalyan 

USMT against a bitlocker partition when starting from PXE

$
0
0

Hoping someone can tell me if there is any special mojo that can make this scenerio work. 

My situation:
I enable Bitlocker encryption as part of my Task Sequence dpeloyment of Windows 7.  I am now diving into USMT (hardlink hopefully) and I quickly realize that i need to "unlock" the bitlocker drive before I can USMT it.  Makes sense.  The disabling Bitlocker as you all know works great when the TS is executed from within Windows.  Where it breaks down for me is that I would like to automate this process even when starting from Windows PE PXE boot
I thought I would be slick and create a vbscript that grabs the enryption key from AD and passes it to manage-bde to unlock the drive.  This works GREAT if you know the computer name (which I was specifying directly in my testing).

The obvious conundrum here is that I cannot retreive the computer name say from the local registry hive, to then pass to the script that queries AD and gets the recovery password since..the drive is locked!

I was really hoping I could query SMBIOS on the machine and take some bit of data and coorelate that to an attribute on the AD object to get the name but have come up empty.

My thought was that I could (although not really wanting to) add a front end the TS that asked for the computername, then runs the script to unlock the Bitlocker partition. 

Anyone else have any tricks up their sleeve?

Thanks!!

Dell Optiplex 9010 All in one bios update.

$
0
0

     I am trying to setup my base windows 7 task sequence to upgrade the bios of an Optiplex 9010 all in one. This is NORMALLY done via a wmi query. Unfortunately, Dell in their infinite wisdom decided to label the system type as Optiplex 9010 for both the desktop/mini tower and the allinone model. The all in one model has its own distinct driver cab, bios updates, etc because the allinone hardware is different. I did some googling around and found that the models can be distinguished by their chassis type. The allinone has a chassis type 13 which literally means "allinone". I found a .vbs, modified it to suit the task sequence needs and inserted it to run in my task sequence while in PE mode just after the "Apply Device Drivers" step. I then placed the bios update package after the machine sets up windows and the config manager and reboots and is installing the base applications. Then it should run if the following is met:



The .vbs is as follows:

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

Dim oTaskSequence, oWMI, colChassis, sChassisType, oChassis
Set oTaskSequence = CreateObject ("Microsoft.SMS.TSEnvironment")
Set oWMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colChassis = oWMI.ExecQuery("Select * from Win32_SystemEnclosure")
For Each oChassis in colChassis
For  Each sChassisType in oChassis.ChassisTypes
  Select Case sChassisType
      Case 8
                Wscript.Echo "Chassis Type: Portable"
                oTaskSequence ("OSDImageType") = "laptop"
            Case 9
                Wscript.Echo "Chassis Type: Laptop"
                oTaskSequence ("OSDImageType") = "laptop"
            Case 10
                Wscript.Echo "Chassis Type: Notebook"
                oTaskSequence ("OSDImageType") = "laptop"
            Case 12
                Wscript.Echo "Chassis Type: Docking Station"
                oTaskSequence ("OSDImageType") = "laptop"
            Case 13 
                Wscript.Echo "Chassis Type: All in One"
                oTaskSequence ("OSDImageType") = "allinone"
            Case Else
                Wscript.Echo "Chassis Type: Unknown"
                oTaskSequence ("OSDImageType") = "desktop"
  End Select
    Next
Next

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

The entire task sequence is relatively simple it is as follows:

  

The bios package is simple as well. It is a package with a program to install the bios patch with the command line of "Optiplex9010A_A08.exe -NOPAUSE -NOREBOOT". 

The log file is not showing errors. Posting below because of screenshot limitations.

Dell BIOS Upgrade to Deployed Clients

$
0
0

Dell BIOS Upgrade.... SCCM!!  I am new at SCCM, any help would be appreciated. 

I downloaded the BIOS for Dell All in One 9010 and 9020, created a SCCM Package and Program.  In command line of Program I have 9010.exe -nopause -noreboot.

I created a WMI query for correct model # and version of bios.  From the WMI query, I created a new collection.  All looks good.  I see both machines I am testing on, in the query and collection (so query statement is working).

I advertise the BIOS Program and the status of advertisement is successful.  I rebooted machines and the BIOS Version is still the older version. UGG.. I must be doing something wrong... any suggestions?? 

Some posts mentioned looking at the logs. Is that logs on the machine I am testing or the logs on the sccm server?

Thanks

WMI becomes corrupt during OSD

$
0
0

Hi all,

I'm having a problem where WMI is becoming corrupt at some point during OSD. It seems to occur prior to installing software packages. The errors I'm getting in smsts.log are:

Failed to open WMI Namespace 'root\ccm\policy\defaultmachine\requestedconfig'. WMI Repository may be corrupted Invalid namespace (Error: 8004100E; Source: WMI)TSManager8/22/2011 12:02:50 PM2776 (0x0AD8)

Error compiling client config policies. code 8004100ETSManager8/22/2011 12:02:50 PM2776 (0x0AD8)

Task Sequence Manager could not initialize Task Sequence Environment. code 8004100ETSManager8/22/2011 12:02:50 PM2776 (0x0AD8)

Task sequence execution failed with error code 8004100ETSManager8/22/2011 12:02:50 PM2776 (0x0AD8)

Now the system actually boots and works ok after this, and they even seem to communicate with the SCCM server fine (for instance, in installing new advertisements). However, because of the WMI failure I'm missing all the software installation steps in the TS. I looked around for info on these errors and what I could find pertained to WMI becoming corrupt at a future point after a successful OSD. Maybe I'm just looking for the wrong terms? I'd sincerely appreciate any help that can be offered. Thank you all.

PXE Boot Help

$
0
0
I am taking over OSD for an SCCM 2007 R2 environment, existing Operating System Images have been created (Win 7 x64), Boot.wim images, drivers, etc and it all works fine for existing models of PCs.  A NEW model of machine has been purchased and is being deployed that we need to PXE OSD but the NIC drivers for this machine we're not loaded.  I followed the MS KBs to obtain and extract the correct driver INF files from the vendor site to the drivers folder on the SCCM network share, add the drivers in configman console, update the driver package, edit the task sequence and update the WIM image.  Everything went successful (assuming that's all that needs to be done).  However, when I PXE boot one of these new machines out of the box I get the following error during boot after pressing F12: Pending request ID: 5306 contact your administrator (which sadly is me now).  when this error passes, the splash screen loads and then I get a no NIC drivers error.  I cant seem to locate a 5306 error code message, can anyone help or provide any insight?  Thanks,

80072EE2 - Retrieving Policy for this computer - fails

$
0
0

after several attempts my boot image works fine and starts the pre-TASKSEQ, i enter a password and then i get....

 

Retrieveing policy for this computer ..... after approximately 2-3 minutes... I get a 80072EE2 error FAILED TO get POLICY.

As this looks like a general issue i went back tru the video guide form The Deployment Team video archive and checked all i did.

Confirmed i followed their procedure to the letter but still the issue happens... can anyone shed some light on this or point me to an article and the correct log file to look at... cheers

 

 SCCM R2 2007- windows 2008R2 domain, SQL 2008R2 DB, etc..

SITE MODE MIXED

ALL roles except DB are on same server.

vmware vCenter Server is sharing this server and it is using http80/https433.

I have the default IIS site using 9080 and 9443 and told config mgr to use these ports.

 

BSOD when updating boot image

$
0
0

I'm trying to right click my boot image and add a driver to it. When it goes thru the process, the SCCM server BSOD's.

Is there any logs I can look at to see what's happening?

OSD Error

$
0
0

We are trying to build an HP Z620 workstaion using a Windows 7 x64 Professiona SP1 image. 

The 64 bit drivers for the network card and stroage have been injected into the boot image and distributed to all DP's.  A new boot media CD has been created for the x64 boot image with the relevant drivers.  When we boot from the CD, the setup process starts but very quickly fails with the following error message

File: \Windows\System32\Drivers\iastor.sys
Status: 0xc0000359
Info: Windows failed to load because of a critical system driver is missing or corrupt.

The iastorA.inf driver has been injected into the boot image (copied to the CD) already and the driver files are in the driver package on the distribution point.  Has anybody encountered this before?

Many thanks

Pam

OSD Task Sequence Fails with Error 0x80091007

$
0
0

Hello Everyone,

I have a bit of a weird hash mismatch problem.  The issue is only occuring on one laptop.  The laptop was imaged successfully, new out of the box.  Computer started "acting craptacular" according to the tech, so he tried to reimage it, assuming one of the applications he put on the computer while setting it up for the user may have messed it up.

From that point forward, the computer couldn't image anymore.  I can image the same model, TS, and even other models without issue.  The error logs are pointing to a hash value mismatch on the OS WIM. 

Here are the log files - I wish there was a way to make them cleaner.  I ran some hardware tests with IBM's PCDoctor, and it came back clean.  I'm starting to run out of ideas.

Thanks in advance!

Log: (SMSTS.LOG)

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

Download done setting progress bar to 100 ApplyOperatingSystem 5/14/2010 4:09:31 PM 840 (0x0348)

Hash could not be matched for the downloded content. Original ContentHash = A6170DC8CFC5A443636828F093C45377B5FE2A62, Downloaded ContentHash = 7DEBC67B90C2326031EF8727238176C92A02006C ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2901) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3000) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3128) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3029) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

TS::Utility::ResolveSource( this->packageID, this->packagePath, TS::Utility::ResolveSourceFlags::PersistContents ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1255) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
resolvePkgSource(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1299) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

Installation of image 1 in package RH1000DD failed to complete..

The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

installer.install(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1373) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RH1000DD ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

The user tries to release a source directory C:\_SMSTaskSequence\Packages\RH1000DD that is either already released or we have not connected to it ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,360) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)

Process completed with exit code 2148077575 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

!--------------------------------------------------------------------------------------------! TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Failed to run the action: XP SP3 - Multi-HAL.

The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Send a task execution status message SMS_TSExecution_ActionFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

MP server rh1-sccm.ritehite.com and port 80. SSL=false. CRL=false. TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Site code: RH1 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Client machine name: R842AEYa TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Client Identity: GUID:428CFC8B-1BE1-4E11-B2C4-21E31EA71572 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Advertisement ID: RH1200C2 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Package ID: RH1000DF TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Sending StatusMessage TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Formatted header: TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>56d444c9-6bf0-4ed2-86a9-5f199c90924c</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T21:09:53Z</SentTime><Protocol>http</Protocol><Body Type="ByteRange" Offset="0" Length="4246"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

CLibSMSMessageWinHttpTransport::Send: URL: sccmserver.x.com:80  CCM_POST /ccm_system/request TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

The request has succeeded. 200 OK TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Set a global environment variable _SMSTSLastActionRetCode=-2146889721 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Clear local default environment TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Let the parent group (Apply Operating System) decides whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Let the parent group (Install Operating System) decide whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Failed to run the last action: XP SP3 - Multi-HAL. Execution of task sequence failed.

The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Cannot run a Task Sequence as the Local Administrator

$
0
0
I would like to Run a Task Sequence Run Command as the Local Administrator, as opposed to running it in the Local System Context.  Is it necessary to specify details of the local Administrator account in the "Run this Step as the Following Account" field?  If so, I notice that it needs to be in the format of Domain\User or %Variable%.  What should the %Variable% value be?

Any ideas?

Timed out waiting for ccmexec service to be fully operational

$
0
0

We are deploying Windows 7 in an SCCM 2007 R3 SP2 environment.  Some of the clients we target fail the task sequence with the error, "Timed out waiting for ccmexec service to be fully operational".  Below is the relevant part of the SMSTS.LOG file:

Succeeded loading resource DLL 'C:\Windows\system32\CCM\1033\TSRES.DLL' 
Failed to create an instance of COM progress UI object. Error code 0x80040154 
Timed out waiting for ccmexec service to be fully operational 
0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,4192) 
Failed to wait for Ccmexec service to be fully operational (0x80004005) 

I have seen several posts with this error that say to create the "ConfigMgr Remote Control Users" group.  Here is an example.  We have created this group locally AND on the domain, but we still see this failure on about 10% of clients that we target.  Any other ideas what might be creating this issue?

Thanks,

FP

Format USB disk error with create stand alone media

$
0
0

To support remote computers we would like to use USB keys to distribute the task sequence.  When I run through the create stand alone media wizard for USB it gets to the point where it will format and fails.  The error in the CreateTSMedia.log is:

Format failed (0x8004242D) CreateTsMedia 12/9/2010 5:33:39 PM 1528 (0x05F8)
Error formatting volume K:\ (0x8004242d) CreateTsMedia 12/9/2010 5:33:39 PM 1528 (0x05F8)
Failed to create media (0x8004242d) CreateTsMedia 12/9/2010 5:33:39 PM 1528 (0x05F8)

I am running Windows 7 x64 with SCCM 2007 R2 SP2.  The USB device is 64 GB in size, I've tried formatting it as NTFS and exFAT with the same results.  The help file indicates with Vista that the disk must be formatted prior to use, but does not indicate how it should be formatted, I assume the same is true for Windows 7.

Any thoughts?


Bob

Capture media not working

$
0
0

I created a capture media to capture windows server 2008 r2 installation and while running it failed.

Below are the smsts logs for the error. Pls guide

Failed to query firmware type.
Wait Callback (Error: D0000004; Source: WinHTTP) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
GetBootInformation(info), HRESULT=d0000004 (e:\nts_sms_fre\sms\framework\tscore\firmware.cpp,165) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
GetType(eType), HRESULT=d0000004 (e:\nts_sms_fre\sms\framework\tscore\firmware.cpp,195) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Firmware::IsMbr(bIsFirmware), HRESULT=d0000004 (e:\nts_sms_fre\sms\framework\tscore\bootimage.cpp,522) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Unmounting volume Z:\ PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
ValidateSystemPartition(), HRESULT=d0000004 (e:\nts_sms_fre\sms\framework\tscore\bootimage.cpp,897) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Failed to prepare the system partition for staging.
Wait Callback (Error: D0000004; Source: WinHTTP) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
BootImage::PrepareForStaging(sLocalDataPath), HRESULT=d0000004 (e:\nts_sms_fre\sms\framework\tscore\bootimage.cpp,674) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=d0000004 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,933) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Failed to pre-stage WINPE image, hr=0xd0000004 PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
PreStageWINPE(m_bDebug), HRESULT=d0000004 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\prepareos.cpp,1374) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Unable to sysprep the machine, hr=d0000004 PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
pCmd->Sysprep(bActivate, bMsd), HRESULT=d0000004 (e:\nts_sms_fre\sms\client\osdeployment\prepareos\main.cpp,270) PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Sysprep'ing the machine failed, hr=d0000004 PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
De-Initialization successful PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Exiting with error code 4 PrepareOS 12/09/14 15:25:10 2828 (0x0B0C)
Process completed with exit code 4 TSManager 12/09/14 15:25:10 2708 (0x0A94)

Dell E6430s OS deployment error

$
0
0

Hey guys. I was wondering if anyone had some insight on a issue i am having with os deployment to a e6430s laptop.

I am getting the following error at the stage setup windows and Confgmgr. I think it might be a driver issue.

1. I imported the dell cabs driver but got the same error.

2. I extracted the cab file and then imported the drivers same error

3. manually downloaded the driver and tested and got error at applying driver package.

Was wondering if anyone had some insight. Thanks guys.

This is the error log below.

The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group (Build the Reference Machine) with the error code 2147500037
Action output: ce\unattend.xml
Successfully initialized driver information
Command line for extension .EXE is "%1" %*
Set command line: "C:\_SMSTaskSequence\Packages\DAN00099\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
Executing commandline: "C:\_SMSTaskSequence\Packages\DAN00099\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
Process completed with exit code 31
Windows Setup completed with exit code 31
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\DAN00099
reference count 1 for the source C:\_SMSTaskSequence\Packages\DAN00099 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\DAN00099
Released the resolved source C:\_SMSTaskSequence\Packages\DAN00099
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)
Exiting with code 0x80004005
Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error

Diagnosing Multicasting & possible DP Issue?

$
0
0

Hi All,

We currently have 2x DPs configured for multicasting with the OS images & their associated advertisements configured accordingly. 

We're observed some odd issues where machines are PXE booting and the countdown (we have set at 5 minutes or 10 clients) counts down to 271 seconds and hangs there... then say it's opening a multicast session... then the timer resets back to the beginning and it starts again? There's definitely 10+ PCs doing this at the same time so it's not a case of there not being enough to start the session in <5 minutes. This happens a few times then it starts to 'download' but none of the machines are seemingly in sync, they just seem to give up and start 'multicasting'. Looking at wdsutil it's clear machines who fall into this weird state aren't actually using multicasting.

What's interesting, is where we were seeing this issue on one occasion, we removed the OS image from DP1, so it was only on DP2, and multicasting worked as expected.

With another image we found the odd issue, we decided to replicate this 'solution', taking the OS image from DP2 and leaving it only on DP1 and unfortunately the weird 271 seconds stall issue occurred.

I'm trying to think of where to start. One thing was to understand a bit more about, in a scenario where an OS image is on both DPs - what is the logic in place to decide which DP a machine will decide to pull the image from?

Thanks for any thoughts.

Update: I've now read this http://technet.microsoft.com/en-us/library/bb632366.aspx which indicates, given our current configuration, that the two DPs would be treated entirely equal as they are configured identically, and although exist on separate subnets, neither of this subnets is shared by our clients.

Software Updates and SCUP updates are not getting rolled out during system rebuild.

$
0
0

Hi,

I am trying to rebuild the machines for one of my client and i am getting below error during Software update stage as it throws below error, Could someone please let me know why the below updates are getting failed.

=======================[ smsswd.exe ] ======================= PackageID = '' BaseVar   = '', ContinueOnError='' SwdAction = '0001' Set command line: Run command line Working dir 'not set' Executing command line: Run command line Process completed with exit code 0 Command line returned 0 
dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526 failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109 Received job completion notification from Updates Deployment Agent  Reboot Required Setting TSEnv variable SMSTSRebootRequested=HD Setting TSEnv variable SMSTSRetryRequested=TRUE Installation is not yet complete, action needs to be re-run after reboot Setting TSEnv variable SMSTSInstallUpdateJobGUID=

109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109  Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 Received job completion notification from Updates Deployment Agent  GetIPriviledgedInstallInterface successful Refreshing Updates Successfully initiated RefreshUpdates operation  Waiting for RefreshUpdates complete notification from UpdatesDeployment Agent Notification received, RefreshUpdates have been completed Signaled RefreshComplete notification Received RefreshUpdates complete notification from Updates Deployment Agent RefreshTargetedUpdates() returned S_FALSE which indicates a non fatal error. Update installation will continue. RefreshUpdates operation has been completed, hr=0x00000001 GetIComponentControllerInterface successful Installation of updates completed successfully Setting TSEnv variable SMSTSInstallUpdateJobGUID= 


I have checked TS logs of few machines and there are few updates which are matching.

Machine1 :

Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109

Machine 2 :

Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5c5e9a15-238b-4df4-b0df-b1b28f2ce658 failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_b688d3c1-ee4b-4e60-83be-3fc10c9985e8 failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 

Machine 3 :

Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5c5e9a15-238b-4df4-b0df-b1b28f2ce658 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_88b882c1-7f9f-45cc-b082-5711f3c94526 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_285710fe-0885-444f-9613-3b2a99529d1c failed with hr = 0x800b0109  
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_f2a02435-7f3a-4c84-a399-80cc4603cbbd failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_5351709c-268c-4986-94e7-a8a8e6e12254 failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_7fd7dfef-c83f-4b17-914f-f2cc362c194b failed with hr = 0x800b0109 
Update with CIID Site_AE7FD70B-82C9-41D8-9890-F8815334FB82/SUM_0558e0fc-5c3c-4a60-99b9-3407cb1b42d0 failed with hr = 0x800b0109 

Dell vsotro 3350 PXE Problem

$
0
0

Hey guys,

I have a network which is included of 80 laptops dell 3350 Vostro and it doesnt boot from PXE.

This is the error message:

TFTP could not connect to server

Could you give me an appropriate solution for this problem?

Viewing all 1063 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>