Re: SMS Virtual Mouse



There could be some conflict between the SMS virtual drivers and your
hardware drivers. I suggest you try to search it at
http://support.microsoft.com/ (try keyword like your hardware model, SMS,
virtual driver and mouse etc...). The most effective way to find the root
cause is to request support from Microsoft support.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

"Waleed" <Waleed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:491E9096-7D87-486F-8E7C-70678B3B43A5@xxxxxxxxxxxxxxxx
> 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: 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)
  • Unable to use Intel Pro 100 with SMS OSD via RIS.
    ... We are trying to use SMS 2003 OSD Feature pack to roll out Windows XP ... Predominantly our site uses two NIC drivers, ... We have updated the WinPE image with the recommended drivers by Intel. ... They include a RIS customised E100B325.inf file which is placed in the ...
    (microsoft.public.sms.tools)
  • Re: The Network Location could not be found Error (800704CF)
    ... Created a custom WinPE folder on the SMS server with the WinPE environment ... I have to boot to the Installation CD for the installation to ... The only way i can get this to work is to add the NIC drivers to the OSD ...
    (microsoft.public.sms.tools)
  • Re: Installing NDIS intermediate without admin rights
    ... you have the info on SMS distribution. ... administrators group to install our NDIS IM driver. ... Unsigned drivers can only be installed by a member of the Administrators group, ...
    (microsoft.public.development.device.drivers)
  • Re: Installing NDIS intermediate without admin rights
    ... administrators group to install our NDIS IM driver. ... Surely MS SMS can ... Unsigned drivers can only be installed by a member of the Administrators group, ...
    (microsoft.public.development.device.drivers)