Re: Testing packages in SMS 2003?

You must mean SMS 2.0, not SMS 2000? Answers in-line:

"Jims" <biz@xxxxxxxxxxx> wrote in message
news:%23SAqqf4mFHA.1048@xxxxxxxxxxxxxxxxxxxxxxx
> We just upgraded an sms 2000 environment to 2003. I am finding it
difficult
> to test packages in 2003. With 2000 I would advertise unassigned packages
> to a PC name or my user account and rerun the package over and over on
> VMWare PCs that I'd reset after each test. I found this to be a very
> efficient test model. I'm having a lot of trouble with this model under
> 2003 and am beginning to regret the upgrade.
> When I try this same test process in 2003 I frequently receive a
program
> error when attempting to rerun a package ("Cannot Run Program" "The
program
> cannot be run because the program files are unavailable. For more
> information please contact your administrator or help desk operator").
I've
> updated the packaged source and deleted the advert with
> rerunadvertisedprogram.vbs with mixed results.
> Questions:
> 1.) What process are experienced 2003 admins using to rapidly test new
> packages?

We have a dedicated QA site to test new packages...

> 2.) How to you force the client to check for new adverts in 2003 (it was
> View|Refresh in Advert prog monitor in 2000).

You can refresh machine policy in SMS 2003 that forces the client to
"check-in" for new policy. You can use the System Management server applet
(control panel), Actions tab, select Machine Policy Retrieval & Evaluation
Cycle (and client intiate action). This can also be scripted.

> 3.) Off the subject; is there a replacement for the cliutils utility in
> 2003? I included this in 2000 packages to run an inventory at the end of
> program execution. It's giving me errors on 2003 clients.

Take a look at www.smsview.com this will let you re-run an advert as well.

Steve


.

Relevant Pages

  • Why wont my msi packages install automatically?
    ... I am distributing many msi packages to clients using sms in my test lab, ... the advert is received from by the client but then ...
    (microsoft.public.sms.swdist)
  • DP update hangs sms_exec after SMS upgrade
    ... updates after upgrading a site from SMS from 2.0 to 2003. ... A little bit of background info: our SMS 2.0 SP5 site had a lot of packages ... No problem with the upgrade or any of the server roles running *except* now ... The work around is to delete the SMS 2.0 packages and recreate under SMS ...
    (microsoft.public.sms.admin)
  • Re: DP update hangs sms_exec after SMS upgrade
    ... Cross posting to swdist newsgroup to see if anyone there has an idea ... SMS 2003 Technical FAQ: ... > packages and as such we opted to upgrade the site to SMS 2003 SP1. ... > The work around is to delete the SMS 2.0 packages and recreate under SMS ...
    (microsoft.public.sms.admin)
  • Re: sms 2 to sms 2003
    ... The easiest way to accomplish this would be to upgrade your sms 2.0 to ... For your packages myitforum.com has a package export script. ... I need to get the queries, collections, packages ...
    (microsoft.public.sms.admin)
  • Re: Transfer sms 2.0 packages to sms 2003
    ... If you mean to upgrade the sms 2.0 site to sms 2003, the packages will be ... intact after the upgrade without you having to do anything. ...
    (microsoft.public.sms.setup)