RE: Software deployment strategy with SMS 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello ,

Thank you for posting.

From your post, my understanding on this issue is: You want to know how to
make SMS clients get software installed ASAP when they join domain. If I'm
off base, please feel free to let me know.

Based on my knowledge, it is a normal behaviour that there is a time delay
between clients' joining domain and their getting advertisements from SMS
Site Server. You can deploy a startup script in your AD domain to force a
policy retrieval cycle on all the client computers. This will force the
client computer to initiate the policy retrieval action on startup and
shorten the time delay. Although this, there still will be some delay due
to the design of SMS system.

If you want to make things perfect, we may deploy those softwares before
you make the system image.

Below is the sample script to force a "Machine Policy Retrieval &
Evaluation Cycle"
================================
'' Create a CPAppletMgr instance
Dim oCPAppletMgr
Set oCPAppletMgr = CreateObject("CPApplet.CPAppletMgr")

'' Get the available ClientActions
Dim oClientActions
set oClientActions = oCPAppletMgr.GetClientActions()
'' Loop through the available client actions

Dim oClientAction
For Each oClientAction In oClientActions

'' Is this the action we want to kickoff?
If oClientAction.Name = "Machine Policy Retrieval & Evaluation Cycle" Then

'' Kickoff the action
oClientAction.PerformAction
End If
Next
================================

For the second question, it appears unrelated to the first one. Would you
please open a new post for the additional question?

Please let me know if you have any other concerns or need anything else.

Sincerely,
Kenxl Zou
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Date: Fri, 07 Apr 2006 11:37:48 +0300
From: "aladdin@xxxxxxxxxxxxxx" <aladdin@xxxxxxxxxxxxxx>
Reply-To: aladdin@xxxxxxxxxxxxxx
User-Agent: Small Wfwg 3.11 News Agent
MIME-Version: 1.0
Subject: Software deployment strategy with SMS 2003
Content-Type: text/plain; charset=ISO-8859-13; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <eAycK6hWGHA.752@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.sms.admin
NNTP-Posting-Host: gw2.lbank.lt 193.219.9.41
Lines: 1
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sms.admin:71980
X-Tomcat-NG: microsoft.public.sms.admin

Hi,

I want to achieve the following. We have preimaged XP Sp2 ghost image
with SMS client. I want to put this image on the clean system, join this
computer to domain and I want SMS to install all required packages for
this XP system. What techniques are you using guys with this situation?
Because I have the following situation that when workstation is joined
to domain collections update after some time and client starts to see
advertised packages only after some time. But our support personnel want
this software installs to appear ASAP, because they want to prepare new
computer for the user ASAP too:) I can hear a lot of their complaints
that advertisments appear only after some time and not right now when
computer is joined to domain, something like with GPO, I can hear
complaints that I'm wasting their time, that the manual install they can
do is faster and so. So I need your advice.

And one more thing - when our support guys prepare new workstations they
are using following procedure - new workstation is named to lets say
NEW1, all software is installed, old workstation is removed from domain
and this new workstation is named to old's workstation name. After this
- they do the same steps again. New workstation is named to lets say the
same NEW1 and procedure repeats. Because of that I have a lot of
duplicated names in SMS console. These names have different guids. And
that is not all - these all names can show as not obsolete:(

What strategy do you use guys in your enterprise to prepare new
workstations with sms. How can I avoid these bad things? Thanks.


.

Relevant Pages

  • Re: Setup client computer over RDP connection? Or how?
    ... Default a fresh install doesn't have RD enabled, so you can't RD to it. ... I can log onto the client computer using the admin account, ... Log into the workstation over RDP, ...
    (microsoft.public.windows.server.sbs)
  • Error Advanced Client setup
    ... I'm having a problem installing the SMS advanced client on certain servers. ... Action start 16:07:53: INSTALL. ...
    (microsoft.public.sms.setup)
  • Re: Advanced Client install nightmare
    ... I can successfully install manually using the SMS account. ... MS Client Configuration Manager cannot install the Advanced Client to ...
    (microsoft.public.sms.admin)
  • Re: Advanced client installed on the client, but not displaying as such on the Admin Console?
    ... Heartbeat Discovery interveral being set so short may have had anything to ... the 2.0 client clean utility). ... client components appear to install (the various icons show up in the ... SMS Client Core Components - Installed ...
    (microsoft.public.sms.admin)
  • Re: General Advice on performance
    ... the SMS client installed some go into the collection that applications are ... PCs to run it when they reboot but this is not an ideal solution. ... don't understand is why they don't get added when they start running the SMS ... Novell's unattended install method to remove the client. ...
    (microsoft.public.sms.swdist)