Jump to content


desek

Established Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

2 Neutral

About desek

  • Rank
    Newbie
  1. As Simo said it works by changing the date. I solved this on my OSD TSes by changing dates between "Setup Windows and ConfigMgr" step. Since I'm running Native Mode I couldn't set the date too far back since it would break the ceritifcate verification. Client Push installations are still not working. At the moment we're pushing clients through a script that changes the date before and after installing the client. Hopefulle there will be a fix soon..
  2. I followed the same guide a couple of months ago. However, with SCCM PXE Point you should copy the files to "\RemoteInstall\SMSBoot" folder and got it working.
  3. To install SCCM 2012 you'll need to update SQL Server to Service Pack 1 and CU4. Be sure to configure SQL Server with the correct colliation. You can read more about the SQL Server requirements on: http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig
  4. Bumped into the same problem today and found some interesting rows in SMSPXE.log: Found Image file: E:\RemoteInstall\SMSImages\ABC00002\boot.ABC00002.wim PackageID: ABC00002 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 2012-04-16 13:54:16 4668 (0x123C) Closing image file E:\RemoteInstall\SMSImages\ABC00002\boot.ABC00002.wim SMSPXE 2012-04-16 13:54:16 4668 (0x123C) It seemed a bit odd to close (read: unmount) the wim before the required bootfiles are copied. My solution was to manually mount the boot wim's to the specified folders with Deployment Tools Commandprompt and the command (Repeated with the package ABC00001): dism /Mount-Wim /WimFile:E:\RemoteInstall\SMSImages\ABC00002\boot.ABC00002.wim /index:1 /MountDir:E:\RemoteInstall\SMSTempBootFiles\ABC00002 To my surprise the PXE worked flawlessly even after I unmounted the wim's and rebooted the server. Before this sulotion fixed my problem I tried to reinstall DP and/or PXE, rebooting the server, manually installing/reinstalling WDS, changing NAA (Computer / SCCM / Domain Admin) without any success. Hope this helps someone!
×
×
  • Create New...