T
Tor Arne Nilsen
I have a little remote deploy scenario, and I can figure out what the best
practice will be. So I hoped someone could give me a little hint.
I have a smaller group of remote computers (Located around in a corp.
WAN/2mbps vpn based on leased lines)
I need to be able to remotely deploy new installations to these clients,
without any user interference at all. I have to be able to remotely trigger
the deployment, and everything has to be done remotely.
All clients are standalone, and they are currently not members of any
domains.
Each client will also be assigned with a static IP address, and hostname.
I was first thinking about a Symantec Ghost solution, but wanted to check if
there is any easier, or more correct way to do this.
Thanks,
-- Tor Arne
practice will be. So I hoped someone could give me a little hint.
I have a smaller group of remote computers (Located around in a corp.
WAN/2mbps vpn based on leased lines)
I need to be able to remotely deploy new installations to these clients,
without any user interference at all. I have to be able to remotely trigger
the deployment, and everything has to be done remotely.
All clients are standalone, and they are currently not members of any
domains.
Each client will also be assigned with a static IP address, and hostname.
I was first thinking about a Symantec Ghost solution, but wanted to check if
there is any easier, or more correct way to do this.
Thanks,
-- Tor Arne