SMS Virtual Mouse

Dear All

Yesterday I faced some problems during the SMS Installation:
I am trying to install Advanced Clients on my workstations running
differents MS OS. We face problems with Windows 2k Pro.
We have Windows 2k with SP2, SP3 and SP4.
we didn't face any problems with Windows XP with XP2.

Steps Done:
---------------
1 - I installed the schema Extended on the Domain Controller holding the
Schema Master
2 - I wait 6 hours till replication is done on all Domain Controllers ( I
Have many Sites)
3 - I installed SMS Server on a server at the Main Office (1 Primary Site
with 1 Server configured to hold all Roles)
4 - I configured Sites Boundaries
5 - I configured Active Directory Discovery
6 - I enable Push Client Installation ( I knew that I should not do this but
it is not the cause of the problem)
7 - I make new collection based on the network subnet
8 - I start Installation of Advanced Client on the collections that I have
created.

Problems: (of course the client have been pushed everywhere):
---------------------------------------------------------------------------
1 - On some computers, The Mouse Stop to response, the SMS Virtual Mouse
makes a conflict with the Mouse Driver specially PS2
2 - On some computers, The drivers of the display is gone and sometimes the
Network card driver too. (All Computers that have this problem are Windows
2000 Pro but with different Service Pack Installed)

Action on Clients to solve Problem:
-----------------------------------------
1 - Unplug the Mouse --> Restart --> Disable the SMS Virtual Mouse -->
Restart --> Uninstall the SMS Virtual Mouse
2 - On the computer that the drivers are lost, we reinstall the drivers.
3 - On some computers, restart is enough, and on other computers restart the
last good configuration.

Action on the SMS Server:
-------------------------------
1 - I disable the Push Client
2 - I remove the SMS Action user (responsible of the installation of the
clients) from the domain admins group
3 - I disable the the Remote tools

Notes:
--------
1 - The SMS Server is working fine
2 - I can get reports about Hardware without no problems
3 - There are 380 clients now
4 - The problem is not general, sometimes we have 43 machines on the same
subnet that are all clients and there is no problem at all, on other subnet
we have 33 machine but only 8 machine infected with different behavior (like
i said above).

Thanks
Waleed
.

Relevant Pages

  • Re: Site question
    ... >User and User group discovery will not interfere. ... >not have a logon script or automated installation method ... clients until you add ... >> from SMS 2.0 due to several reasons. ...
    (microsoft.public.sms.setup)
  • RE: newbie discovery question
    ... GPO installation is supported for Advanced clients (SMS 2003) only. ... If AD Discovery is not available, ...
    (microsoft.public.sms.setup)
  • Clients are not reporting to server.
    ... I have been trying to get SMS 2003 to work for 3 weeks now. ... I have installed a new Windows Server 2003. ... SP1 and pushed clients. ... The Client Push Installation Account is a member of the a security group ...
    (microsoft.public.sms.setup)
  • Re: SMS Virtual Mouse Problem
    ... and they have provided a fix in their more recent drivers. ... > Yesterday I faced some problems during the SMS Installation: ... > 1 - On some computers, The Mouse Stop to response, the SMS Virtual Mouse ... > Action on Clients to solve Problem: ...
    (microsoft.public.sms.admin)
  • Re: What part of SMS inventories the OU-path for computers?
    ... I didn't understand that the System Group Discovery *only* discovers data for the computers in in its own site even if you point out the top of the Active Directory as search path for each site. ... Clients in other sites than the site running the SGD aren't detected/added until the SGD is run for that particular site That is why our clients didn't get their OU-path in SMS until the discovery was run for that particular site. ...
    (microsoft.public.sms.admin)