6 Replies Latest reply on Sep 17, 2018 2:33 PM by Abnranger67

    Machine Mapping with USMT profile restore?

    davidg5700 Specialist

      I've been searching, but haven't been able to answer this question: can Machine Mapping be used to restore a profile with USMT on a new computer?  (We are on 9.6 SP2)

       

      I've played around a bit with the SMA profile restoration and can restore a profile on a new computer using the Machine Mapping.  The negative of SMA is that it is no longer supported by Lenovo and the latest documentation they have is from 2009.  I would rather use an utility that is current and supported.

       

      I have created a template that captures the profile off to a network share and then kicks off another template to load the OS and licensed software with the Machine Mapping tool.  This process works really well and I would like to be able to add the profile restore action to the kicked off template.  When specifying the store to capture the profile to in the capture template, I use the %ldhostname% variable for the store path:  \\server\share\profiles\%ldhostname% .  The launched template with the profile restore action will have a different name and thus the %ldhostname% will be different than the source computer. 

       

      To back up a bit, I create a Bare Metal Server for the new computer (COMPUTER2) and map COMPUTER1 to COMPUTER2 in machine mapping.  We prefer to have a unique name for the second machine, but we would need to keep one machine name through this process, we may consider going that route.

       

      Has anyone done this and if so, how did you do it?

       

      Thanks.

        • 1. Re: Machine Mapping with USMT profile restore?
          MarXtar ITSMMVPGroup

          I don't know of a way within the product to do this.

           

          The mapping information is hel in the PROV_MACHINEMAPPING table of the database. It maps the Computer_Idn values together (basically the ID of each computer in the Computers table).

           

          Unfortunately this information isn't available in the inventory and I can't see a way of accessing it another way without backed SQL work or using a Data Analytics rule.

           

          If you have Data Analytics then you could potentially use an import rule that points to this table and set it to realtime so that when your new machine is added, the source machine gets mapped into a an inventory field. You could then include commands in your template that use variables pointing to this an inventory field. You would therefore either have your USMT capture writing to a file name using the Computer.ID value or have a conversion happening within DA to the computer name so you can have filenames that make more sense.

           

          With DA then this is going to be a fair bit harder.

           

          Mark McGinn

          MarXtar Ltd/MarXtar Corporation

          http://landeskone.marxtar.co.uk

          LANDESK One Development Partner

           

          The One-Stop Shop for LANDESK Enhancements

          • 2. Re: Machine Mapping with USMT profile restore?
            MarXtar ITSMMVPGroup

            FYI - LD10 will have an ability that makes this easier.

             

            Mark McGinn

            MarXtar Ltd/MarXtar Corporation

            http://landeskone.marxtar.co.uk

            LANDESK One Development Partner

             

            The One-Stop Shop for LANDESK Enhancements

            • 3. Re: Machine Mapping with USMT profile restore?
              davidg5700 Specialist

              I surely hope so.  Has there been any estimates for release of v 10? 

               

              I know there tendency is to put out a major release just prior to Interchange in May, but it seems like the chatter for the next release is starting much sooner than it has in the past.

               

              Thanks for the info.

              • 4. Re: Machine Mapping with USMT profile restore?
                MarXtar ITSMMVPGroup

                January most probably based on the most recent info I have.

                 

                Mark McGinn

                MarXtar Ltd/MarXtar Corporation

                http://landeskone.marxtar.co.uk

                LANDESK One Development Partner

                 

                The One-Stop Shop for LANDESK Enhancements

                • 5. Re: Machine Mapping with USMT profile restore?
                  SunnyMol1n1 Rookie

                  I know this is a very old post, but thought I's put this here as I keep finding it in searches for USMT and Machine Mapping.

                  I'm on 2016.0 (I know, planning to upgrade soon) and we are putting together profile transfer with USMT.

                  Took a lot of fiddling, but we finally found that the Device Naming Prompt action will replace the %LDHostName% variable with the Mapped Source name. So we just use then use the %LDHostName% variable in our loadstate command.

                  We have USMT on a preferred server share replicated across our enterprise. So we map a drive H: to the USMT directory, then map a drive J: to a ProfileCache directory on those preferred servers. When we capture a profile we save it to that ProfileCache with a name of the old system's LDHostName. When we capture, we just run Device Name Prompter to reassign %LDHostName% and then point loastate.exe to J:\%ldHostname%.

                   

                  So far, seems to be working like a charm. Hope this helps some of you.

                  1 of 1 people found this helpful
                  • 6. Re: Machine Mapping with USMT profile restore?
                    Abnranger67 Apprentice

                    Hey I like your idea for the USMT, just a little confused of the process. I have used device name prompter, but that is for when I was imaging machines so I can give it a new name. Just not sure how to use that with our USMT script. I was trying to find the option for a private message so we can share. Let me know if you are willing to share your template, thanks in advance. I have been using batch scripts with variables like %1 etc and just pipe them in when I drop the script into a command prompt window so it looks like USMT_Scanstate.cmd <computername>. I appreciate any resource you are willing to share.