RemoteSysInfo - Troubleshooting RemoteSysInfo Connection, WMI con...

http://www.workmoment.com/remote-system-info/remote-system-info-...

Causes for WMI connection failure on the remote computer

Firewall blocks WMI access to the remote computer. The firewall of remote computer must allow Remote Procedure Call (DCOM protocol) and Windows Management Instrumentation (WMI). Add these two to the Exception List of the Firewall. The remote computer is offline. Check if the remote computer is switched ON. The local Administrative privileges on the remote computer must be provided. The user must have rights of the domain administrator to view the details of user computers. WMI-related services has been disabled on the remote PC. The services under "Windows Management Instrumentation Driver Extensions" must be enabled for the purpose. Blank password for the Administrator In Windows XP Professional, accounts with blank passwords are restricted from remote log-in. Either turn OFF the Local Security Policy or provide a valid password to enable the remote access. "Guest Only" feature is turned on. The sharing and security model in windows is set to guest accounts only. On XP Professional or Windows 2003 Server computer the default settings like "ForceGuest" must be turned off. To do this run "secpol.msc" (Local Security Policy Editor), select "Local Policies>>Security Options" and set the feature under "Network access: Sharing and Security model for local computers" to "Classic" if it was set "Guest Only" earlier. Some Versions of Operating Systems won't support WMI Access Windows XP Home Edition. Windows NT cannot connect to an operating system later than Windows 2000, such as Windows XP or Windows Server 2003. Windows 2000 computers must have Service Pack 2 installed to connect Windows XP and later operation systems. Accessing a Windows Server 2003 computer from Windows 98 or Windows 95 is not supported.

Configuring Windows for a successful WMI Connection

Enabling WMI when UAC ( User Access Control) is enabled in Vista or Windows 7 on a remote computer. Open Registry Editor (regedit.exe), open the location "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion \Policies\system", add the DWORD value name "LocalAccountTokenFilterPolicy", and set it's value to "1".

Allowing remote administration in Windows XP. Run "gpedit.msc". Under "Console Root", expand "Computer Configuration" >> "Administrative Templates" >> "Network" >> "Network Connections" >> "Windows Firewall" >> "Domain Profile". Right-click Windows Firewall and set "Allow inbound remote administration exception" to "Enabled" from the right pane.

Grant DCOM Remote Launch permissions under Windows XP. Under "Run", type "DCOMCNFG", and then click "OK". Expand "Component Services" >> "'Computers" >> "My Computer". Right Click on "My Computer" and select "Properties" from the pop-up menu. Then "My Computer Properties" dialog box appears. Select "COM Security" tab. Under "Launch and Activate Permissions", click "Edit Limits". Under "Launch Permission" dialog box, if your name or your group does not appear in the "Groups or user names list" follow these steps: In the "Launch Permission" dialog box, click "Add". Then in the "Select Users", "Computers", or "Groups" dialog box, add your name and the group in the "Enter the object names to select"

3 of 4

11/08/2011 20:12

RemoteSysInfo - Troubleshooting RemoteSysInfo Connection, WMI con...

http://www.workmoment.com/remote-system-info/remote-system-info-...

box, and then click "OK". Under "Launch Permission" dialog box, select your user and group in the "Group or user names" box. In the "Allow" column under "Permissions for User", select "Remote Launch", and then click "OK".

Opening DCOM port Windows XP / Vista / Windows 7. Make sure that local port exceptions are allowed under "Group Policy". Follow the below steps to do this: Under "Run", type "gpedit.msc" and click "OK". Select "Console Root" >> "Computer Configuration" >> "Administrative Templates" >> "Network" >> "Network Connections" >> "Windows Firewall" >> "Domain Profile". Then right click "Windows Firewall: Allow local port exceptions" and then select "Properties". Select "Enable" and click "OK". Hints: Adding Port Exceptions using "Windows Firewall". Open "Control Panel" >> "Windows Firewall" >> "Exceptions" Tab >> "Add Port" >> "Name" box (type "DCOM_TCP") >> "Port Number" box (type "135") >> Select "TCP" option >> Click "OK". You can also type the following command at a command prompt to open a port: "netsh firewall add portopening TCP 135 DCOM_TCP".

Add the program to the Windows Firewall Exceptions list under Windows XP / Vista / Windows 7. Confirm first that the "Windows Firewall: Allow local programs" exceptions setting in Group Policy is enabled before you proceed with defining program exceptions in "Windows Firewall". Follow the below steps to do this: Under "Run", type "gpedit.msc" and click "OK". Select "Console Root" >> "Computer Configuration" >> "Administrative Templates" >> "Network" >> "Network Connections" >> "Windows Firewall" >> "Domain Profile". Then right click "Windows Firewall: Allow local program exceptions" and then select "Properties". Select "Enable" and click "OK".

Configuring WMI under Windows 95,98,Me Editions The DCOM connections must be enabled with WMI application enabled on startup. Open Windows Registry (regedit.exe), under the section "HKLM\SOFTWARE\MICROSOFT\OLE" set the "EnableDCOM" value to "Y", and "EnableRemoteConnect" to "Y". Open Windows Registry (regedit.exe), under the section "HKLM\SOFTWARE\Microsoft\wbem\cimom" ,set the "AutostartWin9X" value to "2" and "EnableAnonConnections" to "1". Place a link "Winmgmt.exe" file into the Startup directory. The file is stored in the "Windows\WBEM" folder.

Home | Products | RemoteSysInfo | Features | Download | Pricing | BuyNow | FAQs | Screenshots | RemoteRegistryCleaner | CybSecureTS Copyright 2008-2011 to WorkMoment, all rights reserved

4 of 4

11/08/2011 20:12