Topic
  • 80 replies
  • Latest Post - ‏2012-10-09T20:57:35Z by PeteCon
SystemAdmin
SystemAdmin
562 Posts

Pinned topic Long and Short of OSD

‏2012-07-02T18:13:13Z |
Woooo love it when IBM takes down the forums mid day for maintenance.

Could someone give me the long and the short of the OS Deployment and what this new MDT Media Creator is and what it means for Bare Metal install?

In the past I had created an image and uploaded it to the TEM server and managed to deploy it out, but the profile did not carry and the resolution was set to 1024X768, just like the PE. But I somehow broke that server and had to rebuild it, so I lost all my work.

Currently we build a master image with Windows 7 x64 and install all of the software and drivers we need and customize it to our needs. Then once this is complete, I have a custom answer file for sysprep that we use, once it has syspreped, we PXE boot it to a Ghost server and upload it.

Then when it is time to image an area, we pxe boot all of the machines and deploy the image out, come back hit ok, then name and join them to the domain.

I understand that the way TEM OSD works, it allows me to push the image and keep it joined to the same domain and with the same name. I have no idea how the new Media Creator works for Bare Metal. That is our only concern. How do we image bare metal machines.

So any help is appreicated.
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-02T18:46:09Z  
    Hi pqill,

    You have two tools you can use depending on your needs - TPMfOSD (http://www-01.ibm.com/software/tivoli/products/prov-mgr-os-deploy/) or Tivoli Endpoint Manager's OS Deployment solution with offers the ability to capture WIM images and Re-Image a computer using a captured WIM image (see the user guide for a more complete description http://pic.dhe.ibm.com/infocenter/tivihelp/v26r1/topic/com.ibm.tem.doc_8.2/OSD_Users_Guide.pdf) . We also provided a tool to generate bootable media called the MDT Media Creator.

    The MDT Media Creator works in the same way that the MDT Bundle Creator works (which is the tool used to generate the deployment share used with our Capture and Re-Image features).

    After you fill out the parameters.ini, and are happy with all the settings, the media creator will generate 3 things:
    1) An MDT Deployment Share
    2) An ISO image that you can then burn to a DVD (if the ISO is small enough to fit on a DVD).
    3) A folder containing all the items you would need to move onto a bootable USB stick.

    After you've burned a DVD or moved the required files to your USB stick, you now have a tool that can be used to to image a computer from any state.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-02T19:03:58Z  
    Hi pqill,

    You have two tools you can use depending on your needs - TPMfOSD (http://www-01.ibm.com/software/tivoli/products/prov-mgr-os-deploy/) or Tivoli Endpoint Manager's OS Deployment solution with offers the ability to capture WIM images and Re-Image a computer using a captured WIM image (see the user guide for a more complete description http://pic.dhe.ibm.com/infocenter/tivihelp/v26r1/topic/com.ibm.tem.doc_8.2/OSD_Users_Guide.pdf) . We also provided a tool to generate bootable media called the MDT Media Creator.

    The MDT Media Creator works in the same way that the MDT Bundle Creator works (which is the tool used to generate the deployment share used with our Capture and Re-Image features).

    After you fill out the parameters.ini, and are happy with all the settings, the media creator will generate 3 things:
    1) An MDT Deployment Share
    2) An ISO image that you can then burn to a DVD (if the ISO is small enough to fit on a DVD).
    3) A folder containing all the items you would need to move onto a bootable USB stick.

    After you've burned a DVD or moved the required files to your USB stick, you now have a tool that can be used to to image a computer from any state.
    When we ghost, our images are 40gigs give or take big. Would this still work with something like a flash drive?
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-02T19:13:59Z  
    When we ghost, our images are 40gigs give or take big. Would this still work with something like a flash drive?
    This would depend on the generated WIM image. WIMs can be quite sizable but typically are much smaller than 40 GB.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T13:11:56Z  
    This would depend on the generated WIM image. WIMs can be quite sizable but typically are much smaller than 40 GB.
    So here is the problem I am having with the OSD.

    I have MDT installed, I have a bundle created, I have WAIK and 7-Zip installed. But when I go to upload the MDT Bundle, it just spins saying "Uploading MDT Resource. Please wait..." It was like this for about 18 hours with no change. Any thoughts or suggestions?
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T16:24:22Z  
    So here is the problem I am having with the OSD.

    I have MDT installed, I have a bundle created, I have WAIK and 7-Zip installed. But when I go to upload the MDT Bundle, it just spins saying "Uploading MDT Resource. Please wait..." It was like this for about 18 hours with no change. Any thoughts or suggestions?
    It looks like something went wrong during the upload. Go ahead and cancel and try again. If you run into the same problem report back and I'll give you some debugging information.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T16:55:33Z  
    It looks like something went wrong during the upload. Go ahead and cancel and try again. If you run into the same problem report back and I'll give you some debugging information.
    Kevin,
    This has happened a couple of times now. I was trying to find some good troubleshooting info, but couldn't find any.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T16:55:38Z  
    It looks like something went wrong during the upload. Go ahead and cancel and try again. If you run into the same problem report back and I'll give you some debugging information.
    Kevin,
    This has happened a couple of times now. I was trying to find some good troubleshooting info, but couldn't find any.
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T17:05:59Z  
    Kevin,
    This has happened a couple of times now. I was trying to find some good troubleshooting info, but couldn't find any.
    Ah okay. Sorry to hear you're running into trouble. We wrote a tool called uploadmanager.exe that, when run, will leave behind a log file. Can you attach a zip of the most recent 5 logs that you find in the directory: %TEMP%\OSDeployment. They will be called something like uploadmanager_1234567910.log

    Perhaps this will shed some light on the problem.
  • JasonHonda
    JasonHonda
    45 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T17:09:07Z  
    Ah okay. Sorry to hear you're running into trouble. We wrote a tool called uploadmanager.exe that, when run, will leave behind a log file. Can you attach a zip of the most recent 5 logs that you find in the directory: %TEMP%\OSDeployment. They will be called something like uploadmanager_1234567910.log

    Perhaps this will shed some light on the problem.
    Another bit of information that might be important. Is there anything special about the connection between the console machine and the server. Proxy in place, etc? The uploadmanager.exe is somewhat of a dumb tool and it might be getting confused by such things.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T17:26:33Z  
    So here is the problem I am having with the OSD.

    I have MDT installed, I have a bundle created, I have WAIK and 7-Zip installed. But when I go to upload the MDT Bundle, it just spins saying "Uploading MDT Resource. Please wait..." It was like this for about 18 hours with no change. Any thoughts or suggestions?
    I had this same issue when uploading. I was not able to spend much time on where the problem was, but I use the provided fixlets to install .Net, 7-Zip and MSXML on the system I was running the console to upload.

    Martin Carnegie
    Gulf Breeze Software Partners
    http://www.gulfsoft.com
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T17:47:59Z  
    Ah okay. Sorry to hear you're running into trouble. We wrote a tool called uploadmanager.exe that, when run, will leave behind a log file. Can you attach a zip of the most recent 5 logs that you find in the directory: %TEMP%\OSDeployment. They will be called something like uploadmanager_1234567910.log

    Perhaps this will shed some light on the problem.
    So, there are no logs in C:\Users{user}\AppData\Local\Temp\2\OSDeployment.

    Only files are
    imageinfoplugin.dll
    uploadmanager.exe
    wimplugin.dll

    I tried running UploadManager from an elevated command prompt but I have no idea which switch to use.
  • JasonHonda
    JasonHonda
    45 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T18:07:26Z  
    So, there are no logs in C:\Users{user}\AppData\Local\Temp\2\OSDeployment.

    Only files are
    imageinfoplugin.dll
    uploadmanager.exe
    wimplugin.dll

    I tried running UploadManager from an elevated command prompt but I have no idea which switch to use.
    That's extremely unfortunate that no logs exist. I'd recommend opening a bug so that we can devote some developer time to working on this issue and so we can work more closely to diagnose the issue.

    Have you tried uploading from another console.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-06T18:09:41Z  
    That's extremely unfortunate that no logs exist. I'd recommend opening a bug so that we can devote some developer time to working on this issue and so we can work more closely to diagnose the issue.

    Have you tried uploading from another console.
    No, I have not. I was trying to upload directly from the server that TEM sits on and not one of the consoles like my PC.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-09T14:21:23Z  
    SO after letting it sit for the weekend, and rebooting the server, the MDT uploaded in a minute with no issues.

    No idea.....
  • JasonHonda
    JasonHonda
    45 Posts

    Re: Long and Short of OSD

    ‏2012-07-09T18:10:38Z  
    SO after letting it sit for the weekend, and rebooting the server, the MDT uploaded in a minute with no issues.

    No idea.....
    I'm sorry that you had trouble with the uploading. We do have intermittent issues with the tool that does the uploading sometimes but have a hard time reproducing. Sometimes as with you, something just needs to restart (dashboard, console, or server).

    A lot of times it takes some interactive sessions to see if we can determine what is going on so we can make fixes for the future. Usually restarting the dashboard or console solves the issue but sometimes not. It obviously depends on the connection from console to server, but it really shouldn't take that long (small packages a few minutes, large WIM images, ~20 minutes in background). This all depends on disk/computer performance and network connection of course. If you think it's not going, you can check task manager on the console and look for uploadmanager.exe. Logs should be generated as we said before %temp%\osdeployment and should be constantly updating while upload is in progress. If dashboard is still uploading but uploadmanager.exe is not, something went wrong and you should restart the dashboard (CTRL+F5) and try again.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T13:55:28Z  
    So now the question is, what am I doing wrong with the PE drivers?
    I downloaded the PE driver pack from Dell and pointed the OSD to that and when the PE starts to boot, it has no network connection and when I check the logs I get this:

    Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS LiteTouch 7/9/2012 3:39:10 PM 0 (0x0000)
    ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 0x80004005 LiteTouch 7/9/2012 3:39:10 PM 0 (0x0000)
    Microsoft Deployment Toolkit version: 5.1.1642.01 LiteTouch 7/9/2012 3:40:08 PM 0 (0x0000)
    GetAllFixedDrives(False) LiteTouch 7/9/2012 3:40:08 PM 0 (0x0000)
    No task sequence is in progress. LiteTouch 7/9/2012 3:40:09 PM 0 (0x0000)
    Unable to find media, prompting to have it reinserted LiteTouch 7/9/2012 3:40:09 PM 0 (0x0000)
    Unable to find media, prompting to have it reinserted LiteTouch 7/9/2012 3:40:11 PM 0 (0x0000)

    Same thing when I point it towards the Windows 7 x64 drivers from Dell
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T15:42:30Z  
    So now the question is, what am I doing wrong with the PE drivers?
    I downloaded the PE driver pack from Dell and pointed the OSD to that and when the PE starts to boot, it has no network connection and when I check the logs I get this:

    Property LogPath is now = X:\MININT\SMSOSD\OSDLOGS LiteTouch 7/9/2012 3:39:10 PM 0 (0x0000)
    ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 0x80004005 LiteTouch 7/9/2012 3:39:10 PM 0 (0x0000)
    Microsoft Deployment Toolkit version: 5.1.1642.01 LiteTouch 7/9/2012 3:40:08 PM 0 (0x0000)
    GetAllFixedDrives(False) LiteTouch 7/9/2012 3:40:08 PM 0 (0x0000)
    No task sequence is in progress. LiteTouch 7/9/2012 3:40:09 PM 0 (0x0000)
    Unable to find media, prompting to have it reinserted LiteTouch 7/9/2012 3:40:09 PM 0 (0x0000)
    Unable to find media, prompting to have it reinserted LiteTouch 7/9/2012 3:40:11 PM 0 (0x0000)

    Same thing when I point it towards the Windows 7 x64 drivers from Dell
    Just to be sure we're on the same page -- are you attempting to use Bootable Media -- or are you using the Re-Image dashboard to attempt a re-image?

    Here comes the obvious question, did you remove the media from the device (hence the prompt)?

    Please zip up all log files you have and attach here.
    Also, what does your parameters.ini look like (the one you used to generate your bootable media content) if you could include that in the zip also, that would be helpful?

    Any customizations? Anything special about the system on which you're deploying (i.e. multiple partitions/disks?)
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T16:44:15Z  
    Just to be sure we're on the same page -- are you attempting to use Bootable Media -- or are you using the Re-Image dashboard to attempt a re-image?

    Here comes the obvious question, did you remove the media from the device (hence the prompt)?

    Please zip up all log files you have and attach here.
    Also, what does your parameters.ini look like (the one you used to generate your bootable media content) if you could include that in the zip also, that would be helpful?

    Any customizations? Anything special about the system on which you're deploying (i.e. multiple partitions/disks?)
    I am attempting to capture an image using the "Capture Images" from inside the Systems Lifestyle.
    I have a laptop next to me with our fully customized image. I modified the sysprep to suit our environment but kept all the important parts of it
    The way I get that error, is that it drops out at a command prompt when it enters PE. I run the LiteTouch.wsf manually and it gives off that error.

    When I run ipconfig, it comes back blank, so I know it is not getting network drivers. I have uploaded 100+ drivers for all the systems. And even pointed the PE drivers to a PE Driver folder provided by Dell. Under Drivers > Make (Dell) > Model (E6520) it shows 14 drivers including E1c6032.inf and E1C62x64.inf and bcmwl6.inf for Net under Class.

    I have attached the logs from the 9th.

    here is the Parameters.ini. I have a Windows 7 x64 listed in the MDT Resources

    general

    1. MDTBundle and DeploymentShare directories will be created beneath this target
    target=C:\BigFixOSD
    overwrite=yes
    debug=0

    network
    #
    1. This section specifies certain network connection parameters, needed to download USMT 3.0.1
    #
    #proxy=
    #proxyUsername=
    #proxyPassword=
    mdtsources
    #
    1. This section specifies the locations of sources that will be used to create the DeploymentShare/MDTBundle
    #
    waiklocation=C:\Program Files\Windows AIK\

    1. Location to the USMT 3.01 MSI files. If not provided, these will be downloaded.
    ;usmt301x86location=
    ;usmt301x64location=

    1. Needed for capturing Windows XP x86
    #windowsXPx86media=

    1. Needed for capturing Windows XP x64
    #windowsXPx64media=

    1. Needed for deploying Windows Vista x86
    #windowsVistax86media=

    1. Needed for deploying Windows Vista x64
    #windowsVistax64media=

    1. Needed for deploying Windows 7 x86
    #windows7x86media=

    1. Needed for deploying Windows 7 x64
    windows7x64media=L:\Source Files\Windows 7 Pro x64
    ##########################################################################################################
    #
    1. Only XP Mass storage drivers are required here
    #
    #xpMassStoragex86
    #location=C:\Drivers\MassStorage\XPx86
    #force=no

    #xpMassStoragex64
    #location=C:\Drivers\MassStorage\XPx64
    #force=no

    Attachments

  • JasonHonda
    JasonHonda
    45 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T17:08:30Z  
    I am attempting to capture an image using the "Capture Images" from inside the Systems Lifestyle.
    I have a laptop next to me with our fully customized image. I modified the sysprep to suit our environment but kept all the important parts of it
    The way I get that error, is that it drops out at a command prompt when it enters PE. I run the LiteTouch.wsf manually and it gives off that error.

    When I run ipconfig, it comes back blank, so I know it is not getting network drivers. I have uploaded 100+ drivers for all the systems. And even pointed the PE drivers to a PE Driver folder provided by Dell. Under Drivers > Make (Dell) > Model (E6520) it shows 14 drivers including E1c6032.inf and E1C62x64.inf and bcmwl6.inf for Net under Class.

    I have attached the logs from the 9th.

    here is the Parameters.ini. I have a Windows 7 x64 listed in the MDT Resources

    general

    1. MDTBundle and DeploymentShare directories will be created beneath this target
    target=C:\BigFixOSD
    overwrite=yes
    debug=0

    network
    #
    1. This section specifies certain network connection parameters, needed to download USMT 3.0.1
    #
    #proxy=
    #proxyUsername=
    #proxyPassword=
    mdtsources
    #
    1. This section specifies the locations of sources that will be used to create the DeploymentShare/MDTBundle
    #
    waiklocation=C:\Program Files\Windows AIK\

    1. Location to the USMT 3.01 MSI files. If not provided, these will be downloaded.
    ;usmt301x86location=
    ;usmt301x64location=

    1. Needed for capturing Windows XP x86
    #windowsXPx86media=

    1. Needed for capturing Windows XP x64
    #windowsXPx64media=

    1. Needed for deploying Windows Vista x86
    #windowsVistax86media=

    1. Needed for deploying Windows Vista x64
    #windowsVistax64media=

    1. Needed for deploying Windows 7 x86
    #windows7x86media=

    1. Needed for deploying Windows 7 x64
    windows7x64media=L:\Source Files\Windows 7 Pro x64
    ##########################################################################################################
    #
    1. Only XP Mass storage drivers are required here
    #
    #xpMassStoragex86
    #location=C:\Drivers\MassStorage\XPx86
    #force=no

    #xpMassStoragex64
    #location=C:\Drivers\MassStorage\XPx64
    #force=no
    Given that you're doing some sort of customization, I think we need a bit more information to know what is going on.

    How are you modifying sysprep? Are you still running the complete Capture action created by the Capture Images dashboard. If everything in that multiple action group is not executed correctly and in order you can have issues. One of the actions is to download and inject the drivers into PE.

    If that is indeed running correctly, and your customization is not interfering with anything, one check is to see if the drivers for your computer model are for PE. Check to see that network and disk (scsi,hdc,...) are for Win7 x64(PE). You can check/uncheck the filters in the Driver Library dashboard to see which drivers are for that make/model for Win 7 x64 to be sure that we will inject into PE those drivers.

    Error looks like it might be related to not finding disk. In PE can you try navigating to c: or d: to see if you have disk drivers. More logs on the machine can be found (c\d\x):\windows\temp\
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T17:43:03Z  
    Given that you're doing some sort of customization, I think we need a bit more information to know what is going on.

    How are you modifying sysprep? Are you still running the complete Capture action created by the Capture Images dashboard. If everything in that multiple action group is not executed correctly and in order you can have issues. One of the actions is to download and inject the drivers into PE.

    If that is indeed running correctly, and your customization is not interfering with anything, one check is to see if the drivers for your computer model are for PE. Check to see that network and disk (scsi,hdc,...) are for Win7 x64(PE). You can check/uncheck the filters in the Driver Library dashboard to see which drivers are for that make/model for Win 7 x64 to be sure that we will inject into PE those drivers.

    Error looks like it might be related to not finding disk. In PE can you try navigating to c: or d: to see if you have disk drivers. More logs on the machine can be found (c\d\x):\windows\temp\
    Here is a copy of my Unattend with all the sensitive info redacted

    The capture action completes on every step and the unit boots to the Bigfix OS Deployment for Windows PE where I just get a command prompt.

    Where would the PE drivers be located on the C drive?
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T17:57:37Z  
    Here is a copy of my Unattend with all the sensitive info redacted

    The capture action completes on every step and the unit boots to the Bigfix OS Deployment for Windows PE where I just get a command prompt.

    Where would the PE drivers be located on the C drive?
    Let's backup. How,exactly, are you providing drivers.

    You should be doing one of the following:

    1) Use Driver Management dashboard and opt to use Driver Management in the Capture Dashboard.
    2) Use field "Path to WinPE drivers" to specify a folder containing all Windows 7 drivers that you found applicable for this machine.

    > JasonHonda wrote:
    > In PE can you try navigating to c: or d: to see if you have disk drivers. More logs on the machine can be found (c\d\x):\windows\temp\

    How did that go? Remember, you can access a command prompt in PE by pressing the F8 key.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T18:05:09Z  
    Let's backup. How,exactly, are you providing drivers.

    You should be doing one of the following:

    1) Use Driver Management dashboard and opt to use Driver Management in the Capture Dashboard.
    2) Use field "Path to WinPE drivers" to specify a folder containing all Windows 7 drivers that you found applicable for this machine.

    > JasonHonda wrote:
    > In PE can you try navigating to c: or d: to see if you have disk drivers. More logs on the machine can be found (c\d\x):\windows\temp\

    How did that go? Remember, you can access a command prompt in PE by pressing the F8 key.
    1) Yes (all 75 Dell Inc drivers uploaded from both the Dell provided PE drivers and the Dell provided Win 7 x64 drivers)
    2) Yes (pointed to a folder of deployable Windows 7 x64 drivers created by Dell)

    PE dumps me to a command prompt right now.

    The X:\Windows\Temp contains the same files I uploaded
    C:\Windows\Temp has a lot of stuff in there, but no OSDLOGS or SMSTSLog folders

    Those folders called Desktop 1.0 or Laptop 3.0 in its original form, are the folders that contain all the drivers we use when we do a driver prep before syspreping the machine to Ghost it.
  • SystemAdmin
    SystemAdmin
    562 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T18:11:54Z  
    1) Yes (all 75 Dell Inc drivers uploaded from both the Dell provided PE drivers and the Dell provided Win 7 x64 drivers)
    2) Yes (pointed to a folder of deployable Windows 7 x64 drivers created by Dell)

    PE dumps me to a command prompt right now.

    The X:\Windows\Temp contains the same files I uploaded
    C:\Windows\Temp has a lot of stuff in there, but no OSDLOGS or SMSTSLog folders

    Those folders called Desktop 1.0 or Laptop 3.0 in its original form, are the folders that contain all the drivers we use when we do a driver prep before syspreping the machine to Ghost it.
    Since I cannot go back and edit a post (note to IBM : Add in an edit post feature)

    Here is a screenshot of my drivers library. Highlighted is the system I am working on.
  • kevin_friedheim
    kevin_friedheim
    26 Posts

    Re: Long and Short of OSD

    ‏2012-07-11T18:27:24Z  
    Since I cannot go back and edit a post (note to IBM : Add in an edit post feature)

    Here is a screenshot of my drivers library. Highlighted is the system I am working on.
    Okay, so it sounds like you have SCSI access in PE, you should also make sure you have NIC (type ipconfig and make sure u get an IP from your DHCP server).

    Next test will be to NOT make ANY customizations and attempt to capture using our capture dashboard. Does that work?

    If you made 5 customizations, try running a capture again...making 1 customization at a time until you've narrowed down the problem. That is what I would do...