Jump to content


anyweb

using System Center 2012 Configuration Manager - Part 7. Build and Capture Windows 7 X64 SP1

Recommended Posts

Have you re-distributed your sources? (OS installers, OS Images)

I also created new task sequences, confirmed NAS account was configured and have access to path.

 

I believe my problem is drivers. (I was under the impression I would not need drivers for a VMware VM)

Share this post


Link to post
Share on other sites

Hello All, I was wondering if someone could give me a hand with an issue I've been having.

 

My task sequence keeps failing when it gets to the point of "Applying Operating System" the error code is 0x080070002. When i press F8 and use CMTrace to look at the SMSTS.log file it shows no errors. It's almost like right after the boot image is loaded it fails. I was wondering if anyone had an idea what could cause this to happen.

 

Things I've done so far:

  • Deleted the Task Sequence and the Windows 7 installation files
  • Recreated both the task sequence and Windows 7 Package in the correct order
  • I've tried using the built in Client Configuration Manager installer as well as Making my own Client Configuration Manager Package. (I've read this can make it fail)
  • When the task sequence fails I've checked to see if i have an IP address by running ipconfig, as well as pinged other computers on the network.
  • Removed and redeployed the task sequences.
  • I've made sure the network access account can access the shares it needs
  • Verified the OS fully transferred to the Primary site from the CAS
  • Tested it (the build&capture) on two different machines with the same results

 

Questions:

  • Right now the physical PC that I'm using to test the deployment on doesn't have an OS anymore because the Task Sequence has partitioned the drive. Does that matter?
  • WDS got installed on my CAS somehow but the service wasn't started, so I removed that role, would that cause any issues?

Any help would be very much appreciated I have not the slightest clue what this could be.

 

Configuration:

CAS - Server 08 R2 - SCCM 2012 - Database Resides on a separate server running SQL08 R2

1st Primary SIte - Server 08 R2 - SCCM 2012 - Database Resides on a separate server running SQL08 R2

2nd Primary Site - Server 08 R2 - SCCM 2012 - Database Resides on a separate server running SQL08 R2

Test PC - Win7 Pro x64 SP1

 

Thanks again.

 

 

UPDATE:

So yesterday I was looking at the wrong SMSTS.log file. turns out the file I needed to be looking at was the SMSTS.Log file that is created on the C: partition. Anyhow, I've updated the log file with the current one. No the issue is its trying to connect to an SMSPKGE$\CAS00012 share.

 

When I try to access that share from within CMD on the box that is having issues using NET USE I get "The network name cannot be found" but I can navigate to that share from any other computer using UNC. Im able to ping my DP but cant access that share from the Testbox...

 

UPDATE #2:

I have solved this issue by switching the NAA and bouncing the server. I was receiving an error on the server itself saying "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again." Once did that everything worked out just fine.

 

Than you all for this wonderful site! I don't think I would have made it with it!

Share this post


Link to post
Share on other sites

Anyone with a lab (or production) with VMWare VMs? I believe I have spent enough days now to determine my problem is drivers.

I have done my homework on how to add VMWare Tools drivers to WinPE, but none of my VMs have a ./Program Files/VMWare/Drivers folder. :(

 

Any suggestion on how can I get past this? If I go through the "hassle" of setting up a Hyper-V server.. will I have the same drivers issue? Is there anything I may be missing?

post-18979-0-01900200-1360275861_thumb.jpg

post-18979-0-24727600-1360276076_thumb.jpg

Share this post


Link to post
Share on other sites

*UPDATE*

 

Started SCCM from scratch. After applying KB2801987 and making sure everything is distributed, it "seems" to be working. It has not error during the Setup Windows & Configuration manager, so let's see if it works.

Share this post


Link to post
Share on other sites

Ok another shot at it tonight and no joy. Now it's not getting even as far as the partitioning and formatting of the drive. I did change the DP to allow anonymous access. My log file from x:\windows\temp\smstslog is attached

 

All and any comments greatly appreciated.

WD

smsts6.txt

Share this post


Link to post
Share on other sites

<![LOG[Failed to create D:\_SMSTaskSequence (1392)]LOG]!><time="19:19:52.394+480" date="02-07-2013" component="TSPxe" context="" type="3" thread="1152" file="utils.cpp:1175">

try diskparting the hard disc, format it and start again

 

in diskpart do like so

 

 

sel disk 0
clean
cre par pri
format fs=ntfs quick
assign
exit
 

Share this post


Link to post
Share on other sites

OK - I decided to wipe clean my SCCM 2012 lab and start from scratch. Downloaded the guides and wrote down a To-Do checklist.

After applying KB2801987 I had to re-deploy the Configuration Manager Client Package

For some reason the task sequences will fail if I have a product key typed in under "Apply Windows Settings" (I am using the right key!)

 

Anyways, I removed the product key, and all the task sequences and capture work flawless (VMWare and Hyper-V) :D

Now to figure out how to tweak the image (Windows settings) and have it ready for my deployment TS via unattend.xml

Share this post


Link to post
Share on other sites

Joy of Joys I'm making progress. 3 times now I've managed to deploy to my virtual machine. But each time it finishes the deployment and then reboots. It doesn't do the capture. Attached are my log files from the virtual machine.

 

I really appreciate all the help. I'm not sure how anyone would learn this software without folks like you.

 

WD

smsts7.txt

smsts7a.txt

smsts7b.txt

Share this post


Link to post
Share on other sites

What would happen if there were multiple task sequences deployed to the same collection. Would pressing F12 bring up a menu of task sequences?

 

yes as long as the computer is in the collection they are deployed to, and as long as the task sequences were deployed with a purpose of Available (optional) and not Required (mandatory)

Share this post


Link to post
Share on other sites

If you use different boot iamges for your task sequences, you also need to add a mandatory reboot ro PE as first step to your sequences.

Share this post


Link to post
Share on other sites

Hi TEam,

 

Can anybody help me.

 

I am receiving the error 0x80091007 Hash value incorrect and mismatch.

 

I have SCCm 2012 Hirearchy

1 CAS

1 primary - MP, DP, SUP

1 Primary - MP, DP, SUP

 

Added Windows Installer distributed the content

 

when i run tasksequence to build and capture image, files gets downloaded successfully but the error HASH MISMATCH

 

Please help me on this

 

Find smsts log.

smsts.log

Share this post


Link to post
Share on other sites

Hi All,


When i distribute boot image content than i facing error in SMSprov.log file.


1}Error setting property (ImageDiskLayout) 0x80041002!


2}Error setting property (TransformAnalysisDate) 0x80041002!


3}Error setting property (TransformReadiness) 0x80041002


We are distribute win 7 os using SCCM 2012 rc in Win2008 R2 server



what should I do?



Br

Share this post


Link to post
Share on other sites

are you really using SCCM 2012 rc ? configuration manager 2012 is already released to RTM and to SP1 level

Share this post


Link to post
Share on other sites

are you really using SCCM 2012 rc ? configuration manager 2012 is already released to RTM and to SP1 level

 

No, I got this one: Microsoft System Center 2012 Configuration Manager Service Pack 1.

 

Then I got this error to: Execute SQL =select all SMS_ObjectContentInfo.DateCreated,SMS_ObjectContentInfo.Description,SMS_ObjectContentInfo.FeatureType,SMS_ObjectContentInfo.LastUpdateDate,SMS_ObjectContentInfo.NumberErrors,SMS_ObjectContentInfo.NumberInProgress,SMS_ObjectContentInfo.NumberInstalled,SMS_ObjectContentInfo.NumberUnknown,SMS_ObjectContentInfo.ObjectID,SMS_ObjectContentInfo.ObjectType,SMS_ObjectContentInfo.ObjectTypeID,SMS_ObjectContentInfo.PackageID,SMS_ObjectContentInfo.SoftwareName,SMS_ObjectContentInfo.SourceSite,SMS_ObjectContentInfo.SourceSize,SMS_ObjectContentInfo.SourceVersion,SMS_ObjectContentInfo.Targeted from fn_ListObjectContentInfo(1033) AS SMS_ObjectContentInfo where SMS_ObjectContentInfo.ObjectID = N'STO00005'

 

What is that one?

 

BR

Share this post


Link to post
Share on other sites

Hello

 

I am hoping someone can help. I am running through the guide (excellent by the way!) and have managed to start the process of building a capturing an image of Windows 7 Enterprise x64 SP1. The process runs through without any issues or errors however it gets to the stage of 'Installing Configuration Manager Client Agent' and then appears to hang. After several minutes it switches to the Windows Log on screen. The image is not captured and there is no .WIM file on the network share.

 

Any help would be appreciated.

 

Regards

 

Paul

Share this post


Link to post
Share on other sites

Ok, I followed the steps (ran into a few issues along the way but got he TS to work somewhat) and got the Build and Capture TS to work ... kind of. It builds out my OS and reboots into Windows and asks me to logon but then never finishes with installing the client or the updates or preforming the capture steps. . .

 

what am i missing ?

 

also, when i'm in windows it made my windows drive 'D:' and not C: ... could this be part of the issue ?

Edited by kmcdougall

Share this post


Link to post
Share on other sites

I have an interesting issue. I am implementing CM2012 with SP1 and decided to split out my distribution point separate from my primary server. I have my x86 and x64 boot images distributed, along with my Windows image for Win7x64-SP1. I created a task sequence and can successfully PXE boot into WinPE, but I stall immediately with an error that the task sequence cannot find the program files on the distribution point. The package ID it references is the "Configuration Manager Client Package".

 

I checked distribution status for the CM client package and it keeps saying it's "in progress" and that it's waiting to be manually pre-staged. I looked at the properties for the package and they are all grayed out -- there is no way to change the prestage setting from its value of manual and everytime I run 'distribute' content, I notice (from the distmgr.log) that it says that the package and its properties have not changed, so nothing is to be done.

 

How else can I get the CM client package to copy to my DPs? Without it, my task sequences are dead on arrival.

Share this post


Link to post
Share on other sites

I have an interesting issue. I am implementing CM2012 with SP1 and decided to split out my distribution point separate from my primary server. I have my x86 and x64 boot images distributed, along with my Windows image for Win7x64-SP1. I created a task sequence and can successfully PXE boot into WinPE, but I stall immediately with an error that the task sequence cannot find the program files on the distribution point. The package ID it references is the "Configuration Manager Client Package".

 

I checked distribution status for the CM client package and it keeps saying it's "in progress" and that it's waiting to be manually pre-staged. I looked at the properties for the package and they are all grayed out -- there is no way to change the prestage setting from its value of manual and everytime I run 'distribute' content, I notice (from the distmgr.log) that it says that the package and its properties have not changed, so nothing is to be done.

 

How else can I get the CM client package to copy to my DPs? Without it, my task sequences are dead on arrival.

 

After all that, I went to Admin > Distribution Points and unchecked "Enable this Distribution Point for Prestaged Content" and all the packages started to flow, including the CM client package I needed.

 

I guess that setting doesn't do what I thought it did, hence my confusion. But looks like I'm in finally in business with my task sequence!

Share this post


Link to post
Share on other sites

I am getting stuck. I am trying to deploy with SP1.

1. With PXE i am getting no OS available.

2. Trying to deploy with ISO and getting no TS available.

 

 

I added Unknown computers to a collection i have TS deployed to.

I added a client by MAC address as well.

 

I can post smsts.log file, but i think all it says that "No assigned task sequence."

 

Here is entry from SMSTS.log file:

Client GUID = GUID:EDB2171B-C5D0-4A7F-B1A3-F36816FF5F90, Netbios name = buildWIn7x2, State = Known

 

Thanks for any help.

post-5093-0-12456700-1362371391_thumb.png

post-5093-0-78939300-1362372163_thumb.png

Share this post


Link to post
Share on other sites

Hi all,

 

I'm running System Center 2012 SP1 as Standalone Primary Site and in my humble opinion It's the most bug-ridden software that I've ever seen.

It runs smoothly once you've got it up and running but getting there is exhausting.

 

I'm trying to get the PXE component up and running for three days now. By the way if you have the sccm client installed the SMSPXE.log is unde %windir\CCM\Logs, don't get the logic...

 

Anyway i get these errors in my SMSPXE.log:

 

 

RequestMPKeyInformation: Send() failed. SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
Failed to get information for MP: http://DCM-SRV-SCCM-01.ulbsibiu.local. 80004005. SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE Provider failed to initialize MP connection.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
RequestMPKeyInformation: Send() failed. SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
Failed to get information for MP: http://DCM-SRV-SCCM-01.ulbsibiu.local. 80004005. SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005 SMSPXE 3/4/2013 9:23:45 PM 2912 (0x0B60)
And these in my distmgr.log when I try to refresh the bootfiles on my DP:
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:53 PM 5572 (0x15C4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:54 PM 5572 (0x15C4)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:54 PM 5572 (0x15C4)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:54 PM 5572 (0x15C4)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:54 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:54 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:55 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:56 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:56 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:56 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:56 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:57 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:57 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:57 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:57 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows\Boot SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002\Windows SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:58 PM 5572 (0x15C4)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\ULB00002 SMS_DISTRIBUTION_MANAGER 3/4/2013 1:38:59 PM 5572 (0x15C4)
What I figured is that when these files get extracted the permissions are incorrectly set. They are owned by the "TrustedInstaller" account and only this account has full rights on the files.
This is clearly a bug, and the permissions must be changed manually every time you update the boot files.
This can be done using PS:
takeown /f D:\RemoteInstall /R /D Y
icacls D:\RemoteInstall /grant SYSTEM:F /t
What I've tried:
1. Uninstalling the MP, PXE, WDS, DP
2. Take ownership of the RemoteInstall folder and reboot
3. Deleting the RemoteInstall folder, Installing the MP, DP, reboot
4. Adding PXE, distribute bootimages
At this point I was getting the same errors and the WSUS service was not starting anymore. (service could not start error 193: 0x1)
Rollback to last snapshot trying a different approach...
I've tried to remove only the PXE service with the same result. (File permissions incorrect in the SMSTempBootFiles folder and RequestMPKeyInformation: Send() failed)
I've tried various combinations of these actions in the last few days all ending with the same result.
I'm at wits end but I do not want to start from scratch and reconfigure everything.
My site is backed up using the Site Maintenance Task, Is there a way to install a fresh server and migrate Collections ADRs, AMPs, Packages and settings?
I am running SCCM 2012 SP1 Standalone Primary Site Server on a VM hosted on VM-ware ESXi, with standard Network Interfaces (E1000)
The database is hosted locally on SQL Server 2012
These are the all my logs:

http://ioan.in/NJq6 - Program Files\Microsoft Configuration Manager\Logs

http://ioan.in/NJgi - Windows\CCM\Logs

I appreciate every bit of help, thank you and sorry for the long post :)

  • Like 1

Share this post


Link to post
Share on other sites

I got it :))


Software Library pane\Task Sequence. Click on it, and at the bottom of the screen you'll see the Deployments tab. On the deployment properties, deployment settings tab.


PXE and ISO both are working.

post-5093-0-45597400-1362459650_thumb.png

Share this post


Link to post
Share on other sites

Hello Gentlemen;

I 'm using MDT2012 integrated SCCM2012 to deploy Windows OSs. I have a very big headache related with regional settings of Windows2012.

The deployed Windows2012 OSs are installed only as En-US regional settings, input locale, timezone, systemlocale...

 

1) TS which is created by using MDT >>> Apply Windows Settings >>> Time Zone >>> (UTC +2:00) Istanbul .

2) I created a settings package and put there unattend.xml and its related portion is as below:

 

<SetupUILanguage>
<UILanguage>tr-tr</UILanguage>
</SetupUILanguage>
<InputLocale>0x0000041f</InputLocale>
<SystemLocale>tr-TR</SystemLocale>
<UILanguage>tr-TR</UILanguage>
<UserLocale>tr-TR</UserLocale>
Could u please advise what I'm missing?
Thanks

Share this post


Link to post
Share on other sites
Hello Again;


1)

I replaced the portion above as shown below:


<SetupUILanguage>

<UILanguage>en-US</UILanguage>

</SetupUILanguage>

<InputLocale>041f:0x0000041f</InputLocale>

<SystemLocale>tr-TR</SystemLocale>

<UILanguage>tr-TR</UILanguage>

<UserLocale>tr-TR</UserLocale>


2) By using dism I set Set-SysLocale:tr-TR , Set-UserLocale:tr-TR , Set-InputLocale:041f:0x0000041f


3) I put the followind line into the customsettings.ini;



TimeZoneName= GTB Standard Time

UserLocale = tr-TR

UserLocale_DefaultUser = tr-TR

KeyboardLocale = tr-TR

KeyboardLocale_DefaultUser = tr-TR

Inputlocale = 041f:0x0000041f

Inputlocale_default = 041f:0x0000041f




...still everything is en-US and Time Zone is Pacific...

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...