W
Can I install MSAS without having it load (as service) so I can use it only on demand?
B
Bill Sanderson
I've wiped out the run entry in the registry relating to the product on one
machine, so that I can use it this way. It does not run as a service, it
runs as a user mode app, which creates a number of the issues noted in these
groups.
There's also a documented way of doing this in the "workaround" paragraph of
this KB article:
http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003
machine, so that I can use it this way. It does not run as a service, it
runs as a user mode app, which creates a number of the issues noted in these
groups.
There's also a documented way of doing this in the "workaround" paragraph of
this KB article:
http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003
W
Walterius
which creates a number of the issues noted in these groups.
Which means what? I don't need any more "issues" in my life.
The other method, the workaround, is stated to be only for Server 2003, and
I am running Windows 2000 Professional.
???
Which means what? I don't need any more "issues" in my life.
The other method, the workaround, is stated to be only for Server 2003, and
I am running Windows 2000 Professional.
???
B
Bill Sanderson
Couple of misunderstanings, I think. The "issues" are related to the
current program being structured as a user mode program, and not as a
service. Nothing you or I can fix, no issues you don't already have! The
workaround is for Microsoft Antispyware--it doesn't matter what OS you are
running it on--it's the same on all of them.
Personally, I'd just pull it out of the run line in the registry--let me
look that up--this is from a Windows 2000 server machine:
HKLM\software\microsoft\windows\current version\run\gcasserv
Just remove that key--to be safe, you could do a File Save of it first.or
you could use MSConfig to block it.
--
current program being structured as a user mode program, and not as a
service. Nothing you or I can fix, no issues you don't already have! The
workaround is for Microsoft Antispyware--it doesn't matter what OS you are
running it on--it's the same on all of them.
Personally, I'd just pull it out of the run line in the registry--let me
look that up--this is from a Windows 2000 server machine:
HKLM\software\microsoft\windows\current version\run\gcasserv
Just remove that key--to be safe, you could do a File Save of it first.or
you could use MSConfig to block it.
--