Push A client using a job
My end goal is to Populate the DS with 50 new computer names, take brand new hp computers out of the box, boot from PXE, Select the computer name from the lsit, then do the following from jobs scheduled in the DS.
Image (join domain using sysprep)
AD has been modified with LDP to put new computers in an OU with policy that turns off the firewall
Push A client install (can this be done?)
Install apps like office 2007
_______________________________________________
So far, all of this works except for the push of the A client. I want to be able to schedule this as a job and just queue it up after the imaging task which has been assigned to a new computer. Should I just put the A agent on the image?
I know there is a push agent tool in both the DS and in the NS, but I don't want to have to do this manually, I want to drag the group of 50 new computers to the image task, then to the push client task, then to the install software task(s).
Comments
I would just put the agent
I would just put the agent onto the image, assuming you are talking about the Deployment server agent. Basically, without the Aclient, the deployment server cannot see the machine when you boot to production and therefore cannot deploy anything to the machines in production.
If your question was answered, mark the anwser as the solution
Give thumbs up if you found a post helpful
Aclient push after imaging is done
If you push an image down without the aclient or dagent installed you will not be able to deploy the agent with a job because once you are in production there is nothing to communicate with the server.
You can copy the aclient.exe and aclient.inp (setup aclient.inp to have all your settings that you want.)
Create a batch file that will run the silent install and
alclient -silent -install \pathtofile\aclient.inp
Usually if the aclient.exe and .inp are in the same directory it will use the appropriate inp file.
Linux Man Viddect
A Client in Image
You do have some options in how you can do this. You can create the image with the Aclient already installed as has already been suggested. If you want your image to be a little lighter, you could include the Aclient install files in the image and set up the image to install it when the machine first boots. If you really want the image to be light, you could Firm in the install files during the imaging process. In that case you'd still need to have the image set up to install the Aclient on first boot.
Unless you have some need to manage the Aclient software separately from the image, it probably makes the most sense to include it in the image already installed. It's simple and it does work.
If you are using NS, you can do the same things with the NS agent.
We've done what you are looking to do. In addition, to get to one image to support all of our hardware platforms, we remove most drivers and supporting software from the base image and firm the appropriate ones in as part of the imaging process. One image supports about a dozen hardware platforms and we have a fully automated build process that includes Office and a half-dozen other applications.
No NS in image!
Unless you know exactly what you are doing, do not put the NS agents in the image. You will create duplicate guids and cause a lot of issues on your NS.
If you know what you are doing, then you can remove the guid information prior to the image process via the registry and posibly other locations.
Would you like to reply?
Login or Register to post your comment.