Re: OSD and USMT and Network Storage

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Michael Niehaus [MS] (mniehaus_at_online.microsoft.com)
Date: 12/23/04

  • Next message: sanko: "OSD Feature Pack problem" 
    Date: Thu, 23 Dec 2004 17:03:17 -0600

    You shouldn't need to set the value in the XML file (as editing that file
    directly is unsupported). Instead, you can use a custom action to set the
    OSDSTATEPATH variable to whatever location you want OSD to use for user
    state backup and restore. By default it will point to a local directory
    (e.g. C:\MININT\SMSOSD\StateStore) but it can be changed to point to a
    network location. The custom action could run:

    osdenv.exe OSDSTATEPATH=\\Server\Share

    or you could run a VBScript that does the same thing:

    Set osd = CreateObject("OSD.Environment")
    osd("OSDSTATEPATH") = "\\Server\Share"

    I believe this is covered to some extent in the OSD User's Guide.

    -Michael Niehaus
     Senior Consultant
     MCS US Centers of Excellence - Deployment AOS
     mniehaus@microsoft.com
     This posting is provided "AS IS" with no warranties, and confers no rights.

    "Todd Mote" <ToddMote@discussions.microsoft.com> wrote in message
    news:E17F6C79-E6ED-42AE-87B1-5B505A65C81E@microsoft.com...
    > Michael
    >
    > Thanks for the post. I too see that section in the xml file and it seems
    > to
    > be in a section that is filled out by things in the GUI, John mentioned on
    > the 16th that the GUI tabfor state migration was taken out, perhaps this
    > is a
    > hold over. I'll assume at this point that saving the state and restoring
    > the
    > state both use this location tag in the xml, I'll try it here shortly. I
    > wonder if some of the solutions presented by John and others will work if
    > you
    > remove that section from the xml file? Like whatever data is in this
    > section
    > trumps anything else. Who knows.
    >
    > Where is your OSDAgent.log? On the client or with the other logs in SMS?
    > I
    > found a bunch of other OSD logs, but not that one.
    >
    > Great post.... I looked through the xml last night, but didn't even see
    > that section.
    >
    > Todd
    >
    > "Michael Bray" wrote:
    >
    >> I have also been tring to backup state data to the network. and to make
    >> it
    >> worse I'be been trying to backup from a System in a workgroup to a domain
    >> server share so the computer account cannot be used to authenticate,
    >>
    >> I had a look in the SMSDeploy.xml file created by the OSD program (in the
    >> OS
    >> package source files) I found a section:
    >>
    >> <StateMigration>
    >> <Location></Location>
    >> <Reserved1></Reserved1>
    >> <Reserved2></Reserved2>
    >> <Reserved3></Reserved3>
    >> </StateMigration>
    >>
    >>
    >> I manually added a the network path I wanted to store the state info into
    >> the <Location>\\server\share\%computername%</Location> section of
    >> SMSDeploy.xml and added a Connect to UNC action to connect to
    >> \\server\share
    >> just before the capture user state action in the State Capture phase.
    >>
    >> And it the user capture then worked. The OSDAgent log recorded:
    >> ****
    >> Loading configuration from \\SMS\SMSPKGD$\ZZZ00001\Install\SMSDeploy.xml
    >> Using state store location from program configuration:
    >> \\server\share\%computername%
    >> No state store credentials were provided in the program configuration.
    >> This
    >> installation will not be able to store state on the network.
    >> ****
    >>
    >> So as it looks to me like onelocation for setting the path for scan state
    >> is
    >> in the SMSDeploy.xml file. But I have found no mention of it except in
    >> the
    >> script examples and there is no entry in the GUI.
    >> I can find nowhere to set the state store credentials mentioned in the
    >> OSDAgent.log unless its in the Reserved1,2 or 3 items in SMSDeploy.xml.
    >> However using the connect to UNC path action with an appropriate account
    >> seems to fix the problem.
    >>
    >> I will continue to investigate but would appreaciate anyone elses
    >> observations.
    >>
    >> Regards
    >> Michael
    >>
    >> "Todd Mote" wrote:
    >>
    >> > I too am trying to get network storage of states to work. I have been
    >> > able
    >> > to get my office 2003 package to install as a state restore action, but
    >> > i
    >> > have not been able to get state migration to work with a network share.
    >> > After reading the OSD guide and setting my state folder with the proper
    >> > permissions, i tried putting everything in the command line per the
    >> > USMT user
    >> > guide, even the network location. I've also attempted to put the
    >> > osdenv.exe
    >> > entry in the preinstall phase to no avail, also in the validation phase
    >> > to no
    >> > avail. i even tried to connect to the unc path entry in the phases
    >> > where i
    >> > could to try to get it to work. I've updated the package and the
    >> > distribution points all to seemingly no difference. Any ideas? Are
    >> > there
    >> > any logs to look at to try to track down the problem?
    >> >
    >> > Thanks in advance...
    >> >
    >> > Todd
    >> >
    >> > "John Lang (MSFT)" wrote:
    >> >
    >> > > Dave,
    >> > >
    >> > > The state migration tab has been removed from the UI. This sets the
    >> > > default
    >> > > state store location to the local hard drive. If you need to store
    >> > > the user
    >> > > state on a network share, please read the section titled: "Planning
    >> > > for
    >> > > User State Migration" in the OSDeployment user's guide.
    >> > >
    >> > > You set the state location by using custom actions. For example:
    >> > > Create a
    >> > > custom action in the pre-install phase OSDENV.EXE
    >> > > OSDSTATEPATH=\\<server>\<share>.
    >> > >
    >> > > This will set the state store location in for use in the State
    >> > > Capture
    >> > > Phase.
    >> > >
    >> > > HTH,
    >> > >
    >> > > John
    >> > >
    >> > >
    >> > > --
    >> > > /----------------------------------------------------------/
    >> > > This posting is provided "AS IS" with no warranties, and confers no
    >> > > rights.
    >> > > OR if you wish to include a script sample in your post please add
    >> > > "Use of
    >> > > included script samples are subject to the terms specified at
    >> > > http://www.microsoft.com/info/cpyright.htm"
    >> > >
    >> > > "Dave Halperin" <Dave_Halperin@bose.com> wrote in message
    >> > > news:OBpbO964EHA.208@TK2MSFTNGP12.phx.gbl...
    >> > > >I was just watching an old webcast, when I noticed that on the image
    >> > > >program
    >> > > > tabs, there is a "state migration" tab where I can set the network
    >> > > > drive
    >> > > > to
    >> > > > store all profile settings. I do not have that on the version I
    >> > > > installed.
    >> > > > Where is it? I downloaded it from Microsoft, not more than 3 weeks
    >> > > > ago.
    >> > > >
    >> > > >
    >> > >
    >> > >
    >> > >

  • Next message: sanko: "OSD Feature Pack problem"

    Relevant Pages

    • Re: OSD and USMT and Network Storage
      ... I too see that section in the xml file and it seems to ... > No state store credentials were provided in the program configuration. ... > installation will not be able to store state on the network. ... > However using the connect to UNC path action with an appropriate account ...
      (microsoft.public.sms.tools)
    • Need help with XML Proxy script
      ... I am trying to change the proxy on ... I tried this XML file ... and converted it to a CPF file using the published ... I also changed 'My Work Network' to 'Work' which according ...
      (microsoft.public.pocketpc.developer)