12 Replies Latest reply on Jul 7, 2008 4:01 AM by jary.busato

    Naming convention in Provisioning

    Rookie

       

      Hi all,

       

       

      anyone know what can i use the naming convention provided by OSD in Provisioning?

       

       

      In OSD, when i deploy a sysprepped image, i can use the COMPANY-nnn naming convention that is what i'm interested, but i need to use the Provisioning and when i deploy the image with prov. template there isn't this option for use similar naming convention....

       

       

      Any idea??

       

       

       

       

       

        • 1. Re: Naming convention in Provisioning
          Rookie

          Interested to see how to do this.

          • 2. Re: Naming convention in Provisioning
            Rookie

            I've found this...

             

            When i've finished the OSD Deploy Script and i go in the advanced view of final script, this may be interesting line:

             

             

             

             

            UseInventoryName=1

             

             

            ComputerNameTemplate=UBI-nnn

             

             

             

             

            AUTOCOMPUTERNAME=UBI-nnn

             

             

             

             

             

             

            REMEXEC33=tokreplw C:\sysprep\sysprep.inf COMPUTERNAME=%Computer - Device Name%

             

             

             

             

             

             

            Now... how can i replicate the execution of this parameter in Provisioning???

            • 3. Re: Naming convention in Provisioning
              bnelson Employee

              When I first started to implement provisioning I was going to find a way to make this work. Then I realized that I had to add at least some info to LANDesk in order to assign the provisioning task. Now I have the pc name as part of my csvimport script. I simply scroll to the bottom of the list and append then next connotation of the PC name. Doing it this way the PC is still named during the imaging process, I just decided what it would be prior to the start of the process.

              • 4. Re: Naming convention in Provisioning
                Rookie

                 

                Yes but this is a manual operation and not the automatized solution...

                 

                 

                Also because we have many images and everyone nedd to have a different naming convention template (image1 > CENTRAL-nnn | image2 > BRANCH1-nnn).

                 

                 

                It's strange and (sorry) stupid that there is a function in OSD and not in Provisioning that have the "image deploy" template!

                 

                 

                I need to implement that part of script in Provisioning...

                 

                 

                • 5. Re: Naming convention in Provisioning
                  Employee

                  There is no default naming convention in provisioning. The best way to name machines is to use a variable (such as ldHostname). I know this is not ideal, and is a little bit lacking compared to the OSD method.

                   

                  If you would like this to change, contact LANDesk support and give them your name and organization info, and ask for this enhancement. It will go to their product marketing team for review. I think it's a good idea.

                  • 6. Re: Naming convention in Provisioning
                    Rookie

                    I know that this feature is not provided by default, but there isn't a way for use the code in REMEXEC script of OSD into Provisioning???

                    • 7. Re: Naming convention in Provisioning
                      Apprentice

                      This is a pretty cool utility that will let you rename the computer a number of different ways using cmdlines.txt during the mini-setup. Might find what you're looking for here

                       

                      http://mystuff.clarke.co.nz/MyStuff/wsname.asp

                       

                       

                       

                       

                       

                      EDIT: Also, in your sysprep.inf if the following are true, you should get what you need

                       

                       

                       

                       

                      [UserData}

                       

                       

                       

                       

                      OrgName = "<COMPANY>"

                      ComputerName = *

                       

                       

                       

                       

                       

                       

                       

                       

                       

                       

                      This makes Windows mini-setup use your <COMPANY> name in the beginning of the hostname followed by a dash and random characters.

                       

                       

                       

                       

                      e.g. "COMPANY-4A6XBE0"

                       

                       

                       

                       

                       

                       

                       

                      ***snipped from Technet @ http://technet2.microsoft.com/WindowsVista/en/library/eb5f258b-98ee-48ee-84a3-51608834b55f1033.mspx?mfr=true

                       

                       

                       

                      Computer_name

                       

                       

                       

                      Specifies the computer name used to access the computer from the network. If ComputerName is missing, you must enter a computer name during Windows Welcome.

                       

                       

                       

                      If you do not specify a value for ComputerName, you must enter a computer name during Windows Welcome.

                       

                       

                       

                      If ComputerName is set to an asterisk () or is an empty string, a random computer name will be generated. If you set this value to an asterisk (), a random computer name is generated. This random name has at most eight characters from the RegisteredOwner and/or RegisteredOrganization strings plus random characters.

                       

                       

                       

                       

                      Computer_name is a string with a maximum length of 15 characters.

                       

                       

                       

                       

                       

                       

                      Message was edited by: ahargreaves

                      • 8. Re: Naming convention in Provisioning
                        Rookie

                         

                        I don't know...

                         

                         

                        I don't know because if i made a OSD Deploy Script, the result is a *.ini file, this INI file is launched by something, or not??

                         

                         

                        What is this "something"??

                         

                         

                        How can i replicate the execution of the script by command line?

                         

                         

                         

                         

                         

                        • 9. Re: Naming convention in Provisioning
                          Apprentice

                           

                           

                          capoitaly wrote:

                          Yes but this is a manual operation and not the automatized solution...

                           

                          Also because we have many images and everyone nedd to have a different naming convention template (image1 > CENTRAL-nnn | image2 > BRANCH1-nnn).

                           

                           

                           

                          It's strange and (sorry) stupid that there is a function in OSD and not in Provisioning that have the "image deploy" template!

                           

                           

                           

                          I need to implement that part of script in Provisioning...

                           

                          The easiest way to do what you're looking for is to use a unique

                          sysprep.inf for each office/location (it sounds like you used different

                          OSD scripts for each location before).

                           

                           

                           

                           

                          Make sure your sysprep looks like this for "CENTRAL-nnn"

                           

                           

                           

                          [UserData}

                          OrgName = "<CENTRAL>"

                          ComputerName = *

                           

                           

                           

                          And for "BRANCH1-nnn"

                           

                           

                           

                          [UserData}

                          OrgName = "<BRANCH1>"

                          ComputerName = *

                           

                           

                           

                           

                           

                          The simple, but frustrating answer is no. Provisioning is not quite the

                          same as OSD, and some things dont work or behave the same. You cannot

                          execute REMEXEC commands in provisioning in general, but there are ways

                          of doing what you want

                           

                           

                          • 10. Re: Naming convention in Provisioning
                            Rookie

                             

                            Uff... bad news...

                             

                             

                            • 11. Re: Naming convention in Provisioning
                              Rookie

                               

                              I've also been working on this, and I'm quite close to porting an OSD .ini script to a Provisioning template.  I'll be happy to post a sanitized XML export of the template when it's complete (a week or two?).

                               

                               

                              Does anyone know where there's a reference to the variables (global or device) that are valid?  And which are applicable to Bare Metal Servers, vs. inventoried devices?

                               

                               

                              Thanks,

                               

                               

                              Peter

                               

                               

                              • 12. Re: Naming convention in Provisioning
                                Apprentice

                                You cannot use naming convention in provisioning but adding %ldHostname% variable to you sysprep.inf (loaded as install script) machines in inventory (insert them with bare metal) keep their names.

                                 

                                HTH,

                                 

                                Jary