WORKSTATION RECYCLING
- From: "Mr Durand" <eldocomp@xxxxxxxxx>
- Date: Thu, 30 Mar 2006 14:26:36 -0700
The policy I have set in place on my network is that we put workstations
through a recycle of sorts when a user leaves the company. When this is
done we use Ghost to make a full backup of the machine and use the same tool
to put a clean image back on the hardware, run Ghostwalker, etc. etc. All
workstations always keep the same name (i.e. DELL123) and we simply reset
computer accounts in the AD. At times the computer will be moved between
OU's based on the department the user works in.
I'm using the advanced client, via push install on all workstations and
given the scenario above...what would be the correct process to keep my site
database correct and a functional client on the machine? The client gets
installed AFTER the machine is imaged and appropriately added to the domain.
Would SMS be smart enough to perform an install/upgrade on the machine and
update the database accordingly if I trigger the installation? Lastly, if
the previous sentence is true, what would happen to software inventory if
for example the old user was using Project 2003 but the new user didn't need
it therefore it was not installed after the machine was rebuilt?
MrDurand
.
- Prev by Date: Re: ADVANCED CLIENT INSTALLED BUT...
- Next by Date: Re: MobileClient.tcf
- Previous by thread: Dump boundaries, discovery, and other configuration settings
- Next by thread: Re: WORKSTATION RECYCLING
- Index(es):
Relevant Pages
|