Re: Software deployment strategy with SMS 2003
- From: Bernard <Bernard@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 17 May 2006 07:48:02 -0700
Chris is right, and aladdin to.
For user-group, use a account only for prestage installation. Ex: "install"
user account. Using such account strategy with no mandatory advertisement let
you control the entire process.
Bern
"Chris" wrote:
Use user-group discovery but don't schedule the advertisements with a.
mandatory install time. This way the package will be available as soon as
user policy retrieval runs but the tech can install it whenever(see Run
Advertised Programs shortcut in control panel).
The system naming/removing from domain/renaming/adding back to the domain
really complicates things for SMS. Why can't the tech just name the system
with the users name initially???
"aladdin@xxxxxxxxxxxxxx" wrote:
And I think it is not good to prestage clients by using user group
membership, because the user which prestages workstation can log on to
other workstation and all of the software tied with this account will be
installed on that workstation:(
Best way I think is to use Ssystem group membership - but here it goes
again - duplicate entries, discovery delays:(
Rune Norberg wrote:
For the renaming issue: SMS uses it's internal GUID to keep track of
clients, meaning it handles renaming of clients. The correct name should be
applied after next HW inventory.
For the staging issue: you missed the clue here; using user groups you don't
have to wait for discovery and collection processing; all information is
"pre-evalutated" in SMS DB. As soon you log on to a workstation as a member
of one or more groups that are member of these collections you should
typically see that the clients start running advertisements about 5 mins.
after logon.
/Rune
<aladdin@xxxxxxxxxxxxxx> wrote in message
news:u7A7sWHWGHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Rune Norberg wrote:
If you don't want to base all of your installations on user groups youI noticed one more bad thing. Our support personnel prepare new computers
can still create a "Computer Prestage" user group and put that one in
those collections where you advertise software you want to prestage on
every computer.
using same names. Let say Support guy No.1 names new workstation TEMP,
joins it to domain, installs all required software through SMS or not,
removes old user workstation from domain and renames this new workstation
to users name. After thess operations he starts to prepare another
workstation using the same TEMP name. Because of that I can see few TEMP
computers names in SMS console:( I even noticed that both of these
computers name have sms clients which are not obsolete:/ I saw the
situation that when the new workstation is joined to domain SMS starts to
install one package few times:/ I think that this happens because of
multiple names in SMS console. So i need advice what technique to use in
preparing new workstations. I want to know how the others uses SMS in such
tasks.
As for your proposed suggestion - there still will be delay:( One delay
when new client is discovered, other delay when group membership is
discovered, other delay when collections are updated. So our support
personnel are angry - they join new workstation to domain and new packages
are available only after sime time:( And untill packages are available
they can't do their job. They can try to refresh policy but this brings
nothing, because sms knows nothing after this new client for some time:(
- Prev by Date: Re: Running programs After SMS package deployment
- Next by Date: Re: for distribution of setup
- Previous by thread: Re: Running programs After SMS package deployment
- Next by thread: How do I add some new "server share" site systems to many or all packages easily?
- Index(es):
Relevant Pages
|
Loading
