Re: Scripting SMS 2003

When you make a site change in the console, it takes some time to become
effective as the various components kick in and do the work needed. If the
change is down the hierarchy, that can take longer.

To reflect this, there are various states for the site control file. I
forget the formal terms, but they're things like "proposed", "applied", etc.
This used to be really obvious in the SMS 1.2 console and you can see it in
some of the logs, the site control inbox, or some of the data structures.

The SMS 2.0 and 2003 consoles take an optimistic approach and show you
the 'proposed' state of the component, so the console reflects your change
right away, even though in reality the change hasn't happened yet and could
conceivably fail. Your script is giving you the actual state. Since you're
monitoring, presumably for success, that's actually a good thing. So I'd
suggest you should keep your script as is.

SMS is a big distributed system, and thus plenty of things don't happen
in real time. That should be acceptable, since managing large numbers of
computers rarely has to happen instantaneously (how important is it that you
upgrade all your users to Office 2003 in the next 30 seconds, for example?).
So I'd suggest it's reasonable to wait a bit before monitoring for success
of site changes.

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

"Peter Lundin" <PeterLundin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E4C2B4AD-F988-41BF-B4A3-F9AE8E877921@xxxxxxxxxxxxxxxx
> Hi,
> After installing a Secondary Site I want to verify that the role
> 'Management
> Point' is enabled.
> To do this I'm querying the 'SMS_SCI_SysResUse' class (se code below).
> The query does not return information that the role is enabled, even
> though
> I can see that it is in the SMS Admin Console, until after 1 to 20
> minutes.
>
> Is this due to intra-site replication or something like that?
> Is there any other way to verify that the role has been enabled without
> the
> delay of 1 to 20 minutes?
>
> ----------
> SiteCode = "mySecSite"
> CentralSiteCode = "myPriSite"
> CentralSiteServer = "myPriServer"
>
> On error resume next
>
> Set loc = CreateObject("WbemScripting.SWbemLocator")
> Set WbemServices = loc.ConnectServer( CentralSiteServer, "root\SMS\site_"
> &
> CentralSiteCode )
> Set objSiteRoles = WbemServices.ExecQuery("Select * From SMS_SCI_SysResUse
> WHERE SiteCode='" & SiteCode & "'")
>
>
> For Each Role In objSiteRoles
> <code>
> Next
> ----------
>
> Regards,
> Peter Lundin


.

Relevant Pages

  • Re: admin console not connecting
    ... connect to the SMS site database. ... Administrator console only from computers that belong to the same domain as ... adding anonymous remote access rights in DCOM ... This account is a member of the local server sms admins group. ...
    (microsoft.public.sms.admin)
  • RE: SMS Admin consoloe hangs on client?
    ... Administrator console running on Windows XP SP 2 still cannot connect to the ... If you run the SMS Administrator ... If you grant anonymous remote access rights, ... > install the same version of the admin console to connect to the site server. ...
    (microsoft.public.sms.admin)
  • Re: Reassign Console
    ... SMS is 9200 while the OS is something ... my other servers connected via this console switch. ... console the server shutdowns down and goes into a reboot. ...
    (AIX-L)
  • Re: remote control database could not be found after Windows 2k3 Sp1 update
    ... The SMS console components are not even installed on the machine. ... remote control database could not be found after Windows ... 2k3 Sp1 update ...
    (microsoft.public.sms.admin)
  • RE: Admin Console problems
    ... Locate the Console root node, expand Component Services, expand ... In Access Permissions, click Edit Limits. ... In Permissions for ANONYMOUS LOGON, ... I am installing the SMS 2003 Admin console on a co-workers workstation from ...
    (microsoft.public.sms.admin)
Loading