Re: Side by Side Upgrade of SMS 2003

Hi Paul,

Yea -- I've found a couple SMS trainers that know nothing other than the
training material, and even that has been questionable! Maybe MS SMS team
should do an "independent" survey about the quality of training provided by
their partners for the Official SMS 2003 course.

Also, don't hesitate to post your questions to the list! We're all here to
help!

Greg


"BogStandard" <BogStandard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E2972AF-7C06-41D7-9602-EA0353FC2DDB@xxxxxxxxxxxxxxxx
> Cheers Greg,
>
> I have nothing in writing but I went on the official Managing SMS 2003
> course. As you do I pumped the trainer for as much additional information
> that would related to my own environment. Myself and a colleague were
> definately told using a different site code would mean the removal first
> of
> of the SMS 2.0 client. We went away and took this as 'gospel.' which was
> obviously a mistake. Saying that I have not come accross anything that
> sayswe
> could just upgrade the client using a different site code.
>
> The deployment methods using the push method I think is just a
> misunderstanding. I had tested in our lab but for whatever reason the
> enabling of the push properties did nothing so I then assumed you then
> deployed using the login script or by sending out to a collection. Back to
> the lab!
>
> Paul
>
> "Greg Ramsey" wrote:
>
>> If you have the articles handy that state SMS 2.0 clients will not be
>> upgraded automatically, please post -- I would like to see what exactly
>> they're referring to.
>>
>> Re: Client Push Installation - remember, when you check the "Enable
>> Client
>> Push Installation to assigned resources", that's when stuff happens
>> automagically. You CAN use the Client Push Installation Wizard to
>> install
>> clients WITHOUT having the "Enable Client Push Installation..." checkbox
>> enabled. So you can control your upgrade using the client push
>> installation
>> wizard, and push to collections.
>>
>> To control my upgrade to SMS 2003 from 2.0, I used 2.0 to install the
>> 2003
>> client. . . In your 2.0 site, just create a package with the proper
>> client.msi and ccmsetup.exe, and create your program with the proper
>> command
>> line to install your client (e.g., "ccmsetup.exe SMSSITECODE=AUTO . .
>> .etc,
>> etc, etc). And then target your SMS 2.0 clients however you wish with
>> 2.0,
>> and upgrade them to 2003. Once they're upgraded to 2003, SMS 2.0 will no
>> longer attempt to reinstall the client. Only one caveat (that I can think
>> of) when installing the 2003 client using 2.0, I don't think you ever
>> receive a "success" status message in your 2.0 system for the advert,
>> because the 2.0 client is no longer there and can't report back success.
>>
>> Greg
>>
>>
>>
>> "BogStandard" <BogStandard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:5CBDE18B-854B-4751-8E7F-F189F19E57EB@xxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > I'm with you on this one as the documentation seems so ambiguous and
>> > vague.
>> > I have read a lot of it.
>> >
>> > I have same deployment issue. I have installed SMS 2003 alongside SMS
>> > 2.0
>> > with a different sitecode and enabled various discovery methods which
>> > worked.
>> > I had intended to control client upgrades via the login script using
>> > capinst.exe. To do this because all users have no admin rights I set up
>> > the
>> > Client Push Installation settings specifying an account that would have
>> > rights to install. Then I thought I could control the installation
>> > using
>> > the
>> > login script test for department x or y thus keeping control. I set up
>> > the
>> > Client Push Installation and SMS 2003 just went off upgrading clients
>> > though
>> > I thought I would have to set up the Client Push Installation settings
>> > for
>> > discovered clients by right clicking on discovered resources and
>> > selecting
>> > 'install client!'
>> >
>> > I don't know if it's me but there seems to be a lot of conflicting
>> > information. I was told specifically on a MS course that clients with a
>> > different site code had to be removed before you could install legacy
>> > or
>> > advanced client with a new site code. The help file in SMS 2003 states
>> > that
>> > the client push will only install where an SMS client is not detected.
>> >
>> > Well for me what has happened has happened and the SMS 2.0 legacy
>> > client
>> > with the old site code has been trashed and the new advanced client
>> > installed
>> > but I didn't control it.
>> >
>> > Mr Confused
>> >
>> > "Pal Singh" wrote:
>> >
>> >> I am really confused about the SMS 2003 Side by Side Upgrade strategy
>> >> as
>> >> some
>> >> articles say that SMS 2.0 clients will not be upgraded automatically
>> >> and
>> >> some
>> >> states yes they will be upgraded if you have overlapping site
>> >> boundaries.
>> >> I
>> >> want to control the deployment of the SMS 2003 Advance Clients and
>> >> would
>> >> like
>> >> to keep the SMS 2.0 Site until all the clients are cutover. We have
>> >> Windows
>> >> XP SP2 and Windows 2000 or higher version of servers. We do have a
>> >> login
>> >> script that have syntax for cliupgrade.exe /enable.
>> >>
>> >> What is the best way to do a control deployment of SMS 2003 Advance
>> >> clients.
>> >> Do I have to do the cliupgrade /disable in the login script(all
>> >> clients
>> >> are
>> >> using the same login script and then push the advance clients to
>> >> slowly.
>> >> My
>> >> migration process is going to take over a month and we do want to get
>> >> HW
>> >> & SW
>> >> inventory from SMS 2.0 clients and SMS 2003 Clients and deploy
>> >> packages
>> >> to
>> >> clients. I have to start testing the deployment this week. Quick
>> >> feedback
>> >> is
>> >> much appreciated.
>> >> Thanks
>>
>>
>>


.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Advanced Client install nightmare
    ... I have previously successfully installed a client over the network, ... I can succesfully connect to the remote registry using the account. ... MVP Windows Server System - SMS ... account specified in the Client push installation properties. ...
    (microsoft.public.sms.admin)
  • Re: Client Push Question - MVP Kim vs Microsoft ?!
    ... My ex-training colleagues referred to me as sms-knowledgeable because I am more often right then wrong when sms is concerned. ... secondary site, I install SMS, configure the site server to be a management ... regarding 3) that enabling both discovery and client push on secondaries will ... > client push installation to get the clients installed. ...
    (microsoft.public.sms.admin)
  • Re: unable to installed software. No rights
    ... installation or find a way in which program can be installed without user ... will indicate to you which program SMS started and when and in next few ... >> client logs which will indicate that SMS has ... >>>> where you add those DPs individually or user preload package tool to ...
    (microsoft.public.sms.swdist)
  • Re: Rolling Out Office 2003 Fails
    ... This is not an SMS issue, but rather an Office 2003 issue when you ... installation on a clean Windows 2003 Server and it runs smoothly, ... Advancec Client tab on the advertisement is set to "run program from ... Software Installation Account. ...
    (microsoft.public.office.setup)
Loading