Re: upgrade to SP2 client with new installation properties

Yes this is it. Thank's Kim. I'll keep that link.

Bernard

"Kim Oppalfens <MVP>" wrote:

I assume you mean this tool:
http://www.myitforum.com/articles/8/view.asp?id=7099

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Bernard" <Bernard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:18E4A28F-EC2E-47C3-AF97-26D6BF4E2E49@xxxxxxxxxxxxxxxx
Hello Marko,

I can help you only on the smscachesize change for clients. You can use a
add-on for the sms administration console. I dont have the url anymore
where
you can get it.
You can write to my Hotmail and I'll send it to you. This is a great tool
that add fonction for advanced client on the admin console, like "Restart
SMS
Agent Host" or "Change cache size" for a collection or a specific
computer.
mattbiondi@xxxxxxxxxxx .

Just put SMSTools in the object.

Bernard

"Marko" wrote:

I am upgrading my SMS 2003 advanced clients from SP1 to SP2, prior to
doing
the SP2 upgrade on my site server and site systems. As part of the
upgrade, I
am trying to get rid of relying on WINS by adding
SMSDIRECTORYLOOKUP=NOWINS
to my client installation properties. This is per Microsoft's
recommendation
in SMS_SP2_SPPlanDeploy.doc. I also want to change to SMSCACHESIZE=2000
from
1000.

I made both changes in SMS Admin Console > Site Hierarchy > Site Settings
>
Client Installation Methods > Client Push Installation > Advanced Client
tab
Installation Properties.

Then I created a package using copies of ccmsetup.exe and client.msi from
SP2, a program with command line "ccmsetup.exe SMSCONFIGSOURCE=U", and an
advertisement. When the advertisement ran on a test computer, the client
got
upgraded to SP2, but cache size stayed at 1000.

I also tried SMSCONFIGSOURCE=PU with the same result.

I know that I can change the cache size by having my clients run a
script,
so I'm not worried about that. But is my new SMSDIRECTORYLOOKUP=NOWINS
setting in force on my upgraded clients? How can I tell?

- Marko



.

Relevant Pages

  • RE: SMS Advanced Client refuses to do its job
    ... [Configuration - Client Properties] ... SMS SMBIOS Serial Number Identifier=43004E0055003700340034003000460050004A00 ... SMS Hardware Identifier=4BE9C601019A00EA ... policy update with 0 assignments" This is correct as there are no adv's for ...
    (microsoft.public.sms.swdist)
  • Re: SP2 Client upgrades
    ... Development SMS with SP2 successfully, however, in my readings, such as in the 'SMS 2003 SP2 Upgrade Checklist', I was under the impression that the clients do not automatically upgrade. ... With this information I prepared a package and found during my testings of my upgrade package push to one test client, ...
    (microsoft.public.sms.admin)
  • RE: Upgrading SMS 2.0 SP5 to SMS 2003 SP2
    ... multiple newsgroups. ... advanced client is different with the previous upgrading process. ... be used to control the client upgrade behavior in your site. ... upgrade automatically from SMS 2.0 to SMS 2003. ...
    (microsoft.public.sms.setup)
  • RE: Since 2003 SP3 upgrade hardware inventory no longer reports me
    ... SMS 2003 SP3 client. ... I did not knowingly restore anything; I did however upgrade from SP1 ...
    (microsoft.public.sms.inventory)
  • Re: sms 2003 advance clients in different AD forest ?
    ... Yes I have defined an Advanced Client Network Access Account, however I noticed in the logs: ... When I try to deploy the Advanced Client to workstations in the other domain that the sms server is not located in, ... sms Primary server in Forest A. ... Windows Server System MVP - SMS ...
    (microsoft.public.sms.setup)