Jump to content


anyweb

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

Recommended Posts

Hello One More Time Guys;

Please ignore my 2 messages above, I figured it out... Now I've another problem.

 

 

I'm using MDT2012 integrated SCCM2012 to deploy Windows Server 2012. All regional settings can be set correctly, input locale, timezone, systemlocale but when a new user (administrator) logs on to Windows Server 2012, the new user's "Format" (time, currency...) and Location (home location) settings are set to English / Unitied States. These settings must be set to the default Format and Location values. How can I set them for new users during deployment?

regionalsettingsproblem.png

Share this post


Link to post
Share on other sites

 

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

 

I just wanted to see if you have had any luck with this. I am getting the MsiEnumRelatedProducts failed message, although my PXE seems to be working fine. I have tried changing permissions and doing various other things, but it seems to make no difference. I'm a bit nervous to keep going forward with this error coming up in the logs, but it does *look* like everything's working okay thus far.

Share this post


Link to post
Share on other sites

I have an issue different from the ones mentioned above. On the step for creating a Task Sequence, After naming the sequence and selecting the 64bit boot image I'm suppose to selcet a package and image on the "Install Windows" step. When I hit browse the list is empty. Any ideas?

Share this post


Link to post
Share on other sites

SP1 changed from the guide that you were probably using. The Task Sequence is looking for the image not the installer. You need to add to the OS image not the OS installer.

I have an issue different from the ones mentioned above. On the step for creating a Task Sequence, After naming the sequence and selecting the 64bit boot image I'm suppose to selcet a package and image on the "Install Windows" step. When I hit browse the list is empty. Any ideas?

Share this post


Link to post
Share on other sites

So I'm working through a build and capture and was having the hardest time. I was getting a lot of the same messages on attempting a PXE boot with my VMware ESX 4.1 VM and SCCM 2012 SP1.

 

First, I needed to make sure that I specified a trusted certificate instaed of the self-signed certificate in the distribution point settings (See http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/2e3d5d45-e9e2-4e8f-a306-ab331927e726/)

 

Second, I needed to let SCCM do the install and configuring of WDS on the distribution point. SCCM still put the RemoteInstall folder on the data volume I created instead of the system volume - maybe because of the NO_SMS_ON_DRIVE.SMS on C:\ or maybe it was because on my first go I had tried to install WDS manually. I did follow removal steps for the PXE feature. Basically, I unchecked those options for the distribution point, let SCCM remove WDS, rebooted the server, removed the old RemoteInstall fodler, and then went back and selected the PXE feature for the distribution point.

 

After that, my VM was booting, but becasue I'm on ESX 4.1, it doesn't play correctly with the WinPE 4.0 boot image. I'm still looking at a workaround for that to get a WinPE 3.0 boot image available.

 

Instead, I asked our desktop support group for an old PC I could test with. Once I added it into the correct colelction, it booted great and the task sequence has gone without issue. The image is about 2 clicks away from finishing the capture process. Oh. It's done :).

 

In the Build and capture, I even got it to update the Win 7 SP1 image with Software updates and isntalled a couple of programs into the image (Office Communicator 2007 R2, Flash 10 and .NET 4 - all from the Software Model portion of the SCCM SDK)

 

On to deploying.

 

Thanks for this forum. It has been REALLY helpful

Share this post


Link to post
Share on other sites

Attempting this with VMWare does not work but trying it on a real PC and I make it to the TS Wizard Password screen. I guess this is MS' way of getting me to use Hyper-V?

 

no, it just means you need a newer version of vmware or add the drivers needed for the boot image. What version of vmware workstation are you testing with ?

Share this post


Link to post
Share on other sites

HI guys,

wondering if anyone has seen this error before. I am attempting to pxe boot a hyperV virtual machine and complete a build and capture. It successfully formats the disk and gets to the applying operating system stage and then halts. This is what is listed in smsts.log

 

 

-Failed to save the current environment block. This is usually caused by a problem with the program.

The parameter is incorrect (Error:80070057)

 

Failed to presist execution state. Error:80070057

 

-Failed to save execution state and environment to local hard disk

Share this post


Link to post
Share on other sites

Niall, after spending another hour on the issue i managed to find a resolution to that error. For future reference for anyone with this issue:

 

Error: Failed to save the current environment block (Error:80070057)

 

Resolution: This is due to the wrong password being entered in the Network Access Account.

Share this post


Link to post
Share on other sites

Is there a way to "pause" the Build & Capture task sequence so I can make customizations and then resume the Task Sequence?

 

I was "taught" to create a Task Sequence within MDT and I can perform cutomizations while in pause.

The problem I am facing is when I deploy that image via regular ConfigMan2012 Task Sequence is that after the deployment the computer is joined to the domain

as a different computer name. :(

 

I found this by verifying the NetSetup.log. The computer has a name of MININT-AA1234 but in AD it is joined as WIN-87KJH.

When I try to log-in with a domain account I get the "The security database on the server does not have a computer account for this workstation trust relation."

Share this post


Link to post
Share on other sites

Hi anyweb

 

i followed the steps but it doesnt work.

 

firstly I have dc01, dc01 (with AD and DHCP) and SCCM all in hyperv,, the servers is on different subnet than workstation,, i give the servers a static ip because the servers subnet without dhcp. so when I created hyperv virtual machine and run it,, it cant get an ip from dhcp..

 

how to connect dhcp with WDS in SCCM?

Share this post


Link to post
Share on other sites

the servers is on different subnet than workstation,

 

 

 

the client needs to be on the same subnet if you want PXE to work, is it ?

Share this post


Link to post
Share on other sites

 

the client needs to be on the same subnet if you want PXE to work, is it ?

 

what do you mean by client? is it the hyperv workstation or the user computer??

if you mean the hyperv which i have my servers its on the same subnet with SCCM,, but the computers are not on the same subnet,, btw i have configured ip helper

Share this post


Link to post
Share on other sites

the computers that you are pxe booting need to be on the same VLAN as the Configuration Manager server hosting the PXE dp

Share this post


Link to post
Share on other sites

Hello,

 

I am having an issue getting a device to connect to the boot image I am running SP1.

 

Bellow is from my SMSPXE.log

 

Machine is running Windows Longhorn. (NTVersion=0X602, ServicePack=0) SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Begin validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Completed validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Initializing PXEPerfObject. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
HTTP is selected for Client. The current state is 0. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Adding WB000002.3 SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Adding WB000005.3 SMSPXE 5/23/2013 10:51:39 AM 5176 (0x1438)
Found new image WB000002 SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Opening image file E:\Images\SMSImages\WB000002\boot.WB000002.wim SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Found Image file: E:\Images\SMSImages\WB000002\boot.WB000002.wim
PackageID: WB000002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Closing image file E:\Images\SMSImages\WB000002\boot.WB000002.wim SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Found new image WB000005 SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Opening image file E:\Images\SMSImages\WB000005\boot.WB000005.wim SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Found Image file: E:\Images\SMSImages\WB000005\boot.WB000005.wim
PackageID: WB000005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Closing image file E:\Images\SMSImages\WB000005\boot.WB000005.wim SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Begin validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
Completed validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
PXE Provider finished loading. SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 5/23/2013 10:51:49 AM 5448 (0x1548)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:51:49 AM 5448 (0x1548)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 5/23/2013 10:52:06 AM 804 (0x0324)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:52:06 AM 804 (0x0324)

 

 

Thanks!

Share this post


Link to post
Share on other sites

so i've followed this guide exactly, and i can't get my vm to pxe boot.

I'm using the rtm of sccm 2012 (not sp1)

i'm using a legacy card (although not really applicable for vmware workstation) i've got dhcp and network boot enabled on a smoothwall to keep this lab seperate from my production.

looking through the settings for WDS it says that pxe is set to ignore all clients is this correct... i've enabled it to see what happens and it doesn't do anything, is there another setting somewhere that needs to be switched on for network boot to work? should WDS be enabled or does sccm use its own deployment system ?

been scratching my head all week over this hope someone can help !

 

thanks

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