none
Right folder configuration for image folder

    Question

  • Hello.

    I am working on a server lab and i have to servers in my network a DC and an app server and they are both Windows Server 2012 R2 DataCenter.on the DC i have DNS, AD DC and so on. and on my app server i have SQL server 2012 enterprise and SCCM 2012 R2.

    I have setup my router to alow TFTP and my client PC finds the router, the server and the boot image but it can't find the install image that i have in my shared folder (\\app-server\system_center$\OS\Client\Windows_7\x64\sources\install.wim). Everytime i try the PC just reboots after trying to start the network connection in Win PE.

    Can some one help me out whit this?

    Saturday, December 28, 2013 10:35 PM

Answers

All replies

  • Are you actually using operating system deployment in System Center Configuration Manager?

    Jason | http://blog.configmgrftw.com

    Sunday, December 29, 2013 2:20 AM
  • Yes. I have added a Windows 7 pro x64 image for unknown machins and a file theres telling what to do. An also shared the system_center$ folder but it like i don't have permissions to open the folder on the network. Even as a administrator.
    Sunday, December 29, 2013 9:40 AM
  • Hi,

    You need to distribute the image to a DP in your site.

    Follow the steps in the blog.

    http://blogs.technet.com/b/anilm/archive/2011/11/26/operating-system-deployment-with-system-center-configuration-manager-2012-beta.aspx


    Juke Chou

    TechNet Community Support

    Sunday, December 29, 2013 3:25 PM
  • If you encounter any trouble when using OSD, the first thing is to get the smsts.log file for investigation.

    Juke Chou

    TechNet Community Support

    Sunday, December 29, 2013 3:26 PM
  • Have you followed any guides?

    ConfigMgr OSD does not pull content from shared directories where you placed source files; it pulls content from distribution points using the network access account. Have you defined a network access account? 

    Not sure what you mean by allowing TFTP -- do you mean you've implemented iphelpers? Once the boot image is downloaded PXE and TFTP are no longer used. 

    Please tell us exactly what steps are being completed and what error messages you are seeing?

    Have you verified that the boot image for the task sequence deployed to the unknown computers collection has the correct NIC driver for the system you are trying to run the task sequence on?

    I highly recommend you review the TechNet documentation or an online guide like those at windows-noob.com.


    Jason | http://blog.configmgrftw.com

    Sunday, December 29, 2013 3:29 PM
  • I have followed a few guides on youtube.

    I run the DHCP server en my router and that one is programed to connect to my app server when theres an PXE recuest.

    And my client gets an IP address, connects to the server, downloads the boot image and loads it just fine. but but when the client try to start the network connection en the boot image it just restarts instet.

    My setup is that i have set a boot image, OS and task to the DP. but the to clients i have tryed whit reboots at the same spot.

    The boot image is version 6.3.9600.16384 and the OS is an RTM Windows 7 Pro x64. culd that be the problem?

    Sunday, December 29, 2013 6:58 PM
  • Does it display an error message before it reboots?  Can you upload the smsts.log file?

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you've found a bug or want the product worked differently, share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".

    Sunday, December 29, 2013 7:31 PM
  • Nope. it just reboots out of no where.

    Where do i finde the smsts.log file?

    Sunday, December 29, 2013 7:43 PM
  • Please answer my two questions:

    Have you defined a network access account?

    Have you verified that the boot image in use has the proper NIC driver?

    For basic troubleshooting, see this post: http://blogs.technet.com/b/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx


    Jason | http://blog.configmgrftw.com

    Monday, December 30, 2013 1:13 AM
  • I have used the administrator account and my own account. I dont know what drivers the image are having but i do know that Windows 7 finds the driver it self after a install to the Lan port.
    Monday, December 30, 2013 8:28 AM
  • That doesn't prove anything though. You need to actually verify it using the technique outlined in the troubleshooting link I posted above which also outlines how to review the smuts.log which others have suggested.

    As for the network access account, it has nothing to do with account you are using: http://www.bing.com/search?q=configuration+manager+2012+network+access+account&form=IE11TR&src=IE11TR&pc=DCJB 

    You should read through some documentation -- OSD is far from a simple process and watching a YouTube video is typically not sufficient to learn the ins and outs and how to simply get it to work.


    Jason | http://blog.configmgrftw.com

    Monday, December 30, 2013 3:50 PM
  • I have been reading a few days on Technet and here on the forum for help on this and i have looked at more than 20 videos telling how to do and why it have to be done like that.. 

    So it's not just one video and just a try.. a have used 4 months on this project whit a lot of reading.. but my english is bit rusty and theres no help to get in danish so my last try to get just a little help was here..

    And the log file do not exist on the systems so i can't get that one to you. sorry.

    Monday, December 30, 2013 6:55 PM
  • The smsts.log *always" exists on the system running the TS.

    Perhaps Kent or Ronni will weigh in here and be able to help you in Danish (via e-mail or some other form).

    My two questions are still there though.


    Jason | http://blog.configmgrftw.com

    Monday, December 30, 2013 6:58 PM
  • I have just made a full search on my Server whith SCCM and there was not a smsts.log file and there was nether one to find on the Client PC.
    Monday, December 30, 2013 7:04 PM
  • But there was a smstsvc.log

    <12-26-2013 21:19:13> INFO: Domain:<PRIVATE.local>, Computer:<APP-SERVER$>.
    <12-26-2013 21:19:13> INFO:ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local>.
    <12-26-2013 21:19:13> ERROR: ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local> return 0.
    <12-26-2013 21:19:13> INFO: Trustee <PRIVATE\Domain Admins>
    <12-26-2013 21:19:13> INFO: Trustee <PRIVATE\APP-SERVER$>
    <12-26-2013 21:19:13> INFO: Domain <PRIVATE>, User account: <APP-SERVER$>
    <12-26-2013 21:19:13> INFO: user:<APP-SERVER$>, Read:0, write:0, delete:1, Full:0.
    <12-26-2013 21:19:13> INFO: User:<APP-SERVER$>, Create Child:1, Delete Child:1.
    <12-26-2013 21:19:30> INFO: Product not found.
    <12-26-2013 21:19:30> INFO: CCM client installed = 0, Major version = 0.
    <12-26-2013 22:28:51> INFO: Domain:<PRIVATE.local>, Computer:<APP-SERVER$>.
    <12-26-2013 22:28:51> INFO:ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local>.
    <12-26-2013 22:28:51> ERROR: ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local> return 0.
    <12-26-2013 22:28:51> INFO: Trustee <PRIVATE\Domain Admins>
    <12-26-2013 22:28:51> INFO: Trustee <PRIVATE\APP-SERVER$>
    <12-26-2013 22:28:51> INFO: Domain <PRIVATE>, User account: <APP-SERVER$>
    <12-26-2013 22:28:51> INFO: user:<APP-SERVER$>, Read:0, write:0, delete:1, Full:0.
    <12-26-2013 22:28:51> INFO: User:<APP-SERVER$>, Create Child:1, Delete Child:1.
    <12-26-2013 22:29:08> INFO: Product not found.
    <12-26-2013 22:29:08> INFO: CCM client installed = 0, Major version = 0.
    <12-26-2013 22:29:47> INFO: Domain:<PRIVATE.local>, Computer:<APP-SERVER$>.
    <12-26-2013 22:29:47> INFO:ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local>.
    <12-26-2013 22:29:47> ERROR: ADsOpenObject <LDAP://CN=System Management,CN=System,DC=PRIVATE,DC=local> return 0.
    <12-26-2013 22:29:47> INFO: Trustee <PRIVATE\Domain Admins>
    <12-26-2013 22:29:47> INFO: Trustee <PRIVATE\APP-SERVER$>
    <12-26-2013 22:29:47> INFO: Domain <PRIVATE>, User account: <APP-SERVER$>
    <12-26-2013 22:29:47> INFO: user:<APP-SERVER$>, Read:0, write:0, delete:1, Full:0.
    <12-26-2013 22:29:47> INFO: User:<APP-SERVER$>, Create Child:1, Delete Child:1.
    <12-26-2013 22:30:03> INFO: Product not found.
    <12-26-2013 22:30:03> INFO: CCM client installed = 0, Major version = 0.
    <12-26-2013 22:30:25> Failed SetExchangePublicKey().
    <12-26-2013 22:30:25> Failed GetExchangePublicKey().

    Monday, December 30, 2013 7:09 PM
  • Please read the troubleshooting OSD post I linked above. It contains all the information you need to get the smsts.log.

    Jason | http://blog.configmgrftw.com

    Monday, December 30, 2013 7:11 PM
  • I have tryed that 3 times now and nothing comes out of it..

    CMD is enable but the client just reboots before i can do enything. it loads the boot image and when it come to start the network connection in the start procces i crashes...

    And theres no report files in SCCM...

    Monday, December 30, 2013 7:19 PM
  • Crashes?

    That's the first you've said that.

    You need to be pressing F8 as soon as WinPE begins to boot to bring up the command-prompt -- don't wait for anything.


    Jason | http://blog.configmgrftw.com

    Monday, December 30, 2013 7:54 PM
  • Hello.

    I am working on a server lab and i have to servers in my network a DC and an app server and they are both Windows Server 2012 R2 DataCenter.on the DC i have DNS, AD DC and so on. and on my app server i have SQL server 2012 enterprise and SCCM 2012 R2.

    I have setup my router to alow TFTP and my client PC finds the router, the server and the boot image but it can't find the install image that i have in my shared folder (\\app-server\system_center$\OS\Client\Windows_7\x64\sources\install.wim). Everytime i try the PC just reboots after trying to start the network connection in Win PE.

    Can some one help me out whit this?

    It has been there from the start...

    I will try that..

    Monday, December 30, 2013 8:19 PM
  • Okay now it tells me theres a DRIVER_VIOLATION error on the client.
    Tuesday, December 31, 2013 3:05 PM
  • I would strip out all unnecessary drivers being injected for this model and try again.  The only things it needs for OSD are access to the network and hard drive.



    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you've found a bug or want the product worked differently, share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".


    • Edited by NPhersonMVP Tuesday, December 31, 2013 3:12 PM
    Tuesday, December 31, 2013 3:12 PM
  • The only hardware in the client is mother board, CPU, RAM, DVD drive and a hard drive and my boot image is the default from the ADK for windows 8.1.

    and after a web seach then it looks like theres some problems whit the boot image for Windows 8.1. maybe that culd be the problem?

    Tuesday, December 31, 2013 3:29 PM
  • "The only hardware in the client is mother board, CPU, RAM, DVD drive and a hard drive"

    Do you have any "Auto Apply Drivers" or "Apply Driver Package" steps in your task sequence?

    "Okay now it tells me theres a DRIVER_VIOLATION error on the client."

    Where is it saying DRIVER_VIOLATION?  If it is in a log, can you post the logs?


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you've found a bug or want the product worked differently, share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".


    • Edited by NPhersonMVP Tuesday, December 31, 2013 3:43 PM
    Tuesday, December 31, 2013 3:42 PM
  • Not at all. Theres only a task for the OS deployment. It comes whit the light blue error screen there tells there was an error there did that Windows neded to restart and id i wanted to know more i culd search for driver violation on the internet.
    Tuesday, December 31, 2013 4:04 PM
  • "Theres only a task for the OS deployment."

    Are you saying there is only one step in your task sequence?

    " It comes whit the light blue error screen "

    Does WinPE start fine and this error comes after applying your OS image?  Did it do this before?

     

     


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you've found a bug or want the product worked differently, share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".


    • Edited by NPhersonMVP Tuesday, December 31, 2013 4:09 PM
    Tuesday, December 31, 2013 4:09 PM
  • This would probably run smoother if you sent us some shots of what your task sequence looks like. Then also monitor the OSD process and see what Task Step it hits before it "crashes". We don't have eyes on what you see so the more information about what you see and when/where you see it at is crucial.

    Dustin Estes - MCP | www.dustinestes.com

    Tuesday, December 31, 2013 4:20 PM
  • This is my task i wil work on a recordning of a VM later
    Wednesday, January 01, 2014 3:25 PM
  • And here is a video of the client.

    http://www.youtube.com/watch?v=K0YVE_Z8tZQ
    • Edited by Jonas Carlsen Wednesday, January 01, 2014 3:48 PM Fixed link
    Wednesday, January 01, 2014 3:47 PM
  • Thanks for the video Jonas. Very helpful. It seems to me that the Boot image is corrupt. You could try creating a new boot image. It could be a driver issue but I doubt it. I would recreate your Boot image and try that. If that doesn't work let us know.

    Dustin Estes - MCP | www.dustinestes.com

    Thursday, January 02, 2014 1:49 PM
  • I have tryed whit an rtm boot image for Windows 7 and then it crashes a littel later. It crashes in the try to start a network connection.
    Thursday, January 02, 2014 6:41 PM
  • What version of SCCM are you running? Where did your boot image in the video come from? What version of ADK are you using?

    Dustin Estes - MCP | www.dustinestes.com

    Thursday, January 02, 2014 6:48 PM
  • SCCM 2012 R2.

    From the ADK to Windows 8.1.

    And the one for Windows 8.1.

    Thursday, January 02, 2014 11:33 PM
  • Did you put any drivers into this boot image? It definitely has to be an issue with the boot image if your machine downloads the WIM fine and then attempts to load the WinPE environment and never makes it then there is an issue with the Boot image. Especially since the error message you are seeing is from Windows 8/8.1 then that means that part of the WIM loaded fine, you are just not able to get into a stable WinPE environment.


    Dustin Estes - MCP | www.dustinestes.com

    Friday, January 03, 2014 1:32 PM
  • The boot image is clean as snow. I have not done enuthing on it.
    Friday, January 03, 2014 5:01 PM
  • Maybe the BIOS isn't configured for optimal Win 8 settings. What is the device you are deploying it to? Is it configured to use proper drive configurations such as AHCI?

    Dustin Estes - MCP | www.dustinestes.com

    Friday, January 03, 2014 5:47 PM
  • Well i don't know if it has the proper configuration but i do know if i take my Windows 7 RTM disk and install that theres no problem. but if i do it via SCCM it crashes after trying to start the network connection with the RTM 7 boot image.

    Saturday, January 04, 2014 1:03 PM
  • You mean you use the WIM file found on the Windows 7 disk as your boot image? Because if that is true then that would be your issue.

    Dustin Estes - MCP | www.dustinestes.com

    Monday, January 06, 2014 8:19 PM
  • That was only for testing. Normaly i user the windows 8.1 boot wim
    Tuesday, January 07, 2014 5:21 AM
  • How exactly do you mean you are using your Windows 8.1 boot wim?

    Dustin Estes - MCP | www.dustinestes.com

    Tuesday, January 07, 2014 1:47 PM
  • Jonas,  ConfigMgr uses WinPE from the Windows Automated Deployment Kit as a boot environment for OSD.  You need to use the boot images that were created by default when you installed ConfigMgr.


    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you've found a bug or want the product worked differently, share your feedback.
    <-- If this post was helpful, please click "Vote as Helpful".

    Tuesday, January 07, 2014 2:22 PM
  • I installed the ADK tool for windows 8.1 in a step for installation of SCCM 2012 R2 and that added the windows 8.1 boot wim that I use for my PXE boot on the client.
    Tuesday, January 07, 2014 2:24 PM
  • That is the correct way. It was just confusing the way you were originally explaining it. Wanted to make sure you weren't under the impression there was a WinPE boot wim on the OS Disk istelf.

    Dustin Estes - MCP | www.dustinestes.com

    Tuesday, January 07, 2014 2:26 PM
  • But it's not working. It's crashing.
    Wednesday, January 08, 2014 11:16 AM