Re: SMS 20003 Install

Hi Kim,

I don't mind disagreement... I am aware of the interactive command, and
stand by my previous statement that installing with standard security mode
is easier to troubleshoot/debug. Once that is working properly it is fairly
simple to change the security mode to advanced.

There are not that many accounts that get created in SMS 2003. It's
certainly nowhere near as bad as SMS 2.0...

To each his (or her) own :)

Steve
"Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1d1b8482fd417644989f3d@xxxxxxxxxxxxxxxxxxxxxxx
>
> Steve,
>
> I am affraid I still disagree with you here, I find advanced security
> easier to troubleshoot since there are less accounts involved.
>
> I suspect you find it more difficult to troubleshoot because you don't
> know how to run tasks as local system. If you open up a dos prompt as
> local system and launch any troubleshooting tasks from this window then
> you can perfectly verify whether the machine account has the necessary
> permissions to do what it needs to do.
>
> Opening up a dos prompt as local system can be done by scheduling a
> cmd.exe using the at command.
>
> at 15:30 /interactive cmd.exe
> Assuming the schedule service is started this should open a command box
> runnign as local system, whenever you type in anything that needs to
> happen remotely (remote registry access, file share mapping,...) the
> localsystem will use the computer account to connect.
>
> If you don't have the schedule service running, and are not allowed to
> run it, then you could always google for cmdasuser which is a tool that
> does exactly the same.
>
> PS: You do need local admin privileges for this to work.
>
> Would that make troubleshooting advanced security easier, or are there
> still things you think of that you can't do this way? If so, please
> explain, because of this is a stumble block for people going to advanced
> security then we need to have this addressed.
>
> Thanks for the help.
> Kim Oppalfens
> MVP SMS
>
> In article <#ay5EIEcFHA.1504@xxxxxxxxxxxxxxxxxxxx>,
> stevethompson@xxxxxxxxxxxxx says...
> > Installing with Advanced Security mode creates more difficulties in
> > troubleshooting if the installation goes bad.
> >
> > Steve
> > "Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:MPG.1d176c918ee64eaa989efc@xxxxxxxxxxxxxxxxxxxxxxx
> > >
> > > I agree with point 2 the site server computer account have to be in
the
> > > local administrators group of the sql server.
> > >
> > > I mainly responded because I think the advice to start with standard
> > > security and then upgrade is not a very good one. It would leave you
> > > with a lot of unused user caccounts you have to clean up afterwards.
> > > My advice would be to install in advanced security whenever possible,
> > > just make sure you met all the requirements. SQL 2000 SP3A and give
the
> > > site server machine account local admin access on all site systems not
> > > running on the site server.
> > >
> > > Kim Oppalfens
> > > MVP SMS
> > > In article <eercKzEbFHA.2180@xxxxxxxxxxxxxxxxxxxx>,
> > > stevethompson@xxxxxxxxxxxxx says...
> > > > Why not install with standard security first, then upgrade to
advanced
> > > > security once you verify everything is working.
> > > >
> > > > Have you added your SMS site server computer account in the SQL
server's
> > > > local Administrators group?
> > > >
> > > > Steve
> > > >
> > > > "Leigh Morgan" <Leigh Morgan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
> > > > news:CF782A53-DA83-4EFE-B1E2-DE7428ED3540@xxxxxxxxxxxxxxxx
> > > > > Hi,
> > > > >
> > > > > My SMS2003 install is stopping at "Installing Windows Management
> > > > providers"
> > > > >
> > > > > I am installing with advanced security, with the database residing
on
> > a
> > > > > different server to the sms site server and the sms provider on
the
> > site
> > > > > server. I have checked the log files and found the following in
the
> > > > > smsprov.log:
> > > > >
> > > > > [E84][Wed 06/08/2005 08:55:02]:<*><*> CANT CONNECT TO SQL,
RETURNING
> > ERROR
> > > > > <*><*>
> > > > > [E84][Wed 06/08/2005 08:55:02]:Found IClassManger: Opal SMS CSsp
> > Provider
> > > > > Extension Implementation.
>
> --
> Kim Oppalfens
> SMS MVP


.

Relevant Pages

  • Re: SMS 20003 Install
    ... know how to run tasks as local system. ... localsystem will use the computer account to connect. ... Would that make troubleshooting advanced security easier, ...
    (microsoft.public.sms.setup)
  • Re: IE 6.0 on Windows 2000 Closes Unexpectedly when opened
    ... with IE- security, antivirus, ad-blockers, toolbars & other add-ons, etc. ... You may have to uninstall then reinstall, or not reinstall, a program. ... the "clean boot" troubleshooting method may help you find the ... No warning message, no error ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Re: Extremely slow boot and lots of errors
    ... then the screen is black for the other 15 min. and the error message ... "Failure- Security Options- Logon process has failed to create the ... do clean-boot troubleshooting to ...
    (microsoft.public.windows.vista.general)
  • Re: Sharing and security TAB missing
    ... Microsoft MVP [Windows XP Shell/User] ... Windows® XP Troubleshooting http://www.winhelponline.com ... There is no option of security or sharing... ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: SceCli Event ID 1202 error - Local System
    ... Ihave 3 different domains with default configuration and also with high security configuration for the DC's. ... But on NONE of them is local system added to the "Create a token object" user right. ... getting the above error about the Local System account. ...
    (microsoft.public.windows.server.active_directory)