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

[IT-Operation]

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

[SLCollege]

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

[kmcdougall]

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 February 21, 2013 by kmcdougall

[wildcard78]

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.

[wildcard78]

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!

[ogeccut]

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.

[Ioan Popovici]

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

[ogeccut]

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.

[xnor2001]

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

[xnor2001]

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...