Remote Control

  • Thread starter Thread starter Jeremy Drake
  • Start date Start date
J

Jeremy Drake

Does anyone know if the current BETA can support connecting to other
computers on the network? I have about 3 desktops and 3 laptops on my home
networks and would like to scan them all without having to walk to each
system.
 
Hi Jeremy,

From: "Ron Chamberlin"

As was posted elsewhere, one shouldn't run this on a
production machine. It is neither designed nor intended
at this time for an Enterprise deployment,
or for deployment in an Enterprise.

Additional info on what may happen in an Enterprise
situation can be found here:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;892375

Ron Chamberlin
MS-MVP

Good luck

Engel
20050720 3:05
 
Does anyone know if the current BETA can support connecting to other
computers on the network? I have about 3 desktops and 3 laptops on my home
networks and would like to scan them all without having to walk to each
system.
Click to expand...

You can scan mapped network drives of other computers using your local MSAS,
but this does not provide the same functionality as it provides locally
(i.e. it will not scan remote registry and processes in memory on remote
machines, just files on the mapped drives).
Management functions will be provided in enterprise/corporate version of
MSAS, but the date of the release is still unknown. And more - the managed
(corporate) version will not be free of charge.
 
Has Microsoft decided on what the pricings will be of every edition of MSAS?

I think MSAS has done something to prevent me from mapping drives on my
network. I have disabled the program and services associated with it and
still get the same error. Since XP has a habit of not allowing me to use
other usernames besides Guest, I tried using the command prompt where I get
"Error Number 5". I think MSAS did something to the NET USE command, where
authentication is involved.
 
There will be a version of Microsoft Antispyware which doesn't cost anything
beyond what you've already paid for Windows.

I think you've pretty successfully demonstrated that your problem doesn't
relate to Microsoft Antispyware.

Is this XP Pro, or Home? Is there a password set on the Guest account?
 
It is XP Pro SP2 on both PC's and there is no password on the guest account
at this time.

| There will be a version of Microsoft Antispyware which doesn't cost
anything
| beyond what you've already paid for Windows.
|
| I think you've pretty successfully demonstrated that your problem doesn't
| relate to Microsoft Antispyware.
|
| Is this XP Pro, or Home? Is there a password set on the Guest account?
|
| --
|
| | > Has Microsoft decided on what the pricings will be of every edition of
| > MSAS?
| >
| > I think MSAS has done something to prevent me from mapping drives on my
| > network. I have disabled the program and services associated with it and
| > still get the same error. Since XP has a habit of not allowing me to use
| > other usernames besides Guest, I tried using the command prompt where I
| > get
| > "Error Number 5". I think MSAS did something to the NET USE command,
where
| > authentication is involved.
| >
| >
|
|
 
It is XP Pro SP2 on both PC's and there is no password on the guest
account
at this time.
Click to expand...


Run gpedit.msc, go to Windows settings-> Security settings-> Local policy->
User rights and check whether Guest does not have restricted access to the
computer from the network. And if you did not manually assigned the Guest
account access to the shares, then check also in the Windows settings->
Security settings-> Local policy-> Security options if the rights assigned
to Everyone also apply to Guest (under Network access).
 
You are remembering more about this than I am at the moment. I recall that
network access by an account with no password is restricted by default--but
I've never used the Guest account on an XP system, and I'm not sure what
would be needed to give it full rights--thanks!

--
 
You are remembering more about this than I am at the moment. I recall
that network access by an account with no password is restricted by
default--but I've never used the Guest account on an XP system, and I'm
not sure what would be needed to give it full rights--thanks!
Click to expand...

Thanks for your kind words, but my knowledge is still far, far behind yours
:-)

I personally avoid using Guest account for any purposes, too.
But it is a common problem in small/home networks to gain access to the
shares, when "non-IT" people do not understand differences in user rights
and shares management after they change from Win9x to Win2k/XP/2k3. So
usually the Guest account plays a role in such cases.
And you're right, the account without a password may be a problem, too. This
is what I have forgotten :-)
 
Back
Top