Deployment and Imaging Group

 View Only
  • 1.  Windows imaging takes common name after image deploy

    Posted Aug 04, 2016 10:56 AM

    Hello

    We using Deployment Solution 7.6. We deployed many images earlier as well very smoothly.

    Just now we have seen that on client machine image gets deployed successfully booted into production as per task sequence but each and every time it takes common name like ABC-123456.

    Whenever we deployed image on any model machines it take by default common Hostname only and because of this altiris agent wont register with task server and because of that all the boot to production and other post installation task gets failed.

    When we deploy image on virtual machine it will not take common name this happened only Physical machine.

    Is there any reason why always it takes common hostname when we deply image. 



  • 2.  RE: Windows imaging takes common name after image deploy

    Posted Aug 04, 2016 11:21 AM

    One way to do it is to use the "Apply System Configuration" task to rename and then join to domain right after the image boots back into production. You can set Computer name to use %SERIALNUMBER% if you want to rename the machine to its own serial number.

     

    -Deploy image

    -Boot to (Production)

    -Apply System Configuration (Can do both rename and join to domain)

    -Any other apps/scripts/etc...



  • 3.  RE: Windows imaging takes common name after image deploy

    Posted Aug 04, 2016 11:31 AM

    Hello

    renaming the machine is a different part, we doing that in our post installation task.

    My question is why bydefault machines takes common hostname E.g ABC - 123456



  • 4.  RE: Windows imaging takes common name after image deploy

    Posted Aug 04, 2016 12:13 PM

    What does your Sysprep unattend file look like? There is a section in there to name the PC during mini-setup.

     

    <ComputerName>*</ComputerName>



  • 5.  RE: Windows imaging takes common name after image deploy

    Posted Aug 04, 2016 12:18 PM

    we using default sysprep unattend file.



  • 6.  RE: Windows imaging takes common name after image deploy

    Posted Aug 05, 2016 04:33 PM

    I image a completely different way (no-sysprep) so I checked my unattends on my server. The default unattends do not look like they have any <Computer> node set. So, this would become a Microsoft question as to how it determines the computer name and not an Altiris question as Altiris has no control over the Windows OS naming convention using a sysprep unattend file with no Computer name set.

    You could, and again I do imaging a different way, inject the name into this XML tag at some point. That way the computer will boot to production with a specific computer name. This would take some scripting though.