![]() Set Media Source step and Media Server troubleshootingĪ Build Plan may fail while executing the Set Media Source step if your Media Server is not set up correctly or is not accessible from your deployment network or target server. If that doesn't work, check the failed job log for a listing of the disks, and try setting the custom attribute to the disk you want to capture or deploy to. If it is defined already, you might try removing it and letting the Build Plan set it automatically. If you're doing an image installation, verify that the file exists on the Media Server in the Images folder.Ĭheck the SystemDiskNumber custom attribute. Verify that the WimFileName custom attribute is defined. If you are installing, make sure the target disk is large enough. ![]() If you are capturing, make sure there is space on the Media Server. If you have media server access issues, try running the ProLiant SW - Validate Media Server Settings Build Plan (for details, see Set Media Source step and Media Server troubleshooting).Ĭheck disk space. If you are capturing, make sure you have write access to that folder. Use the command prompt to verify that you have access to Z:\Images. You should be able to do this from the target server's console. Verify that the Media Server is mounted properly. You should be able to tell what types of things you need to look at, such as no access to Media Server, trouble finding the disk to capture/deploy, trouble with the partition table, and so on. There will be no visible status message and no option to enter any commands.Ĭheck the job log to determine where the failure occurred. When the server boots into this mode, you will see an Intelligent Provisioning splash screen only. The Intelligent Provisioning service OS does not allow a command prompt. You should get a command prompt and can begin entering commands.įrom the Intelligent Provisioning Linux service OS The last status message should read Server is now in MAINTENANCE mode. You should see some status information on the system console. Once that is done, click on one of the command prompt windows, bring it to the front, and enter commands. To disable this feature and enable you to bring a command prompt window to the front, click on the Window menu in the Tail application and uncheck Always on top. There are already command prompt windows available on the screen, but they are underneath the Tail for Win32 window. This window is programmed to always be on top of other windows. The status in this window should read Server is now ready for provisioning. The following instructions describe how to do this:įrom a Windows service OS (PXE or Intelligent Provisioning)Ī server in the WinPE service OS will have a window open on the console titled Tail for Win32 that contains status messages. This enables you to verify proper operation of your media server, hard drives, network connections, etc. If you are having trouble with your Build Plans, one of the most powerful troubleshooting steps at your disposal is the ability to enter commands on your system console while the server is still in the service OS. Access the command prompt on your target server while in the service OS
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |