Props

Check out our hombres new blog here:

http://serverteam.blogspot.com/

8)

WMI is broken on Windows XP Service Pack 2

Question/Issue:

VBScript is failing on executing a WMI query, e.g.
Set oWMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")

Solution:

To repair WMI, open a command prompt (you will need to have administrative privileges) and run the following command:

rundll32 wbemupgd, UpgradeRepository

Then, open the services snap-in (services.msc) and restart the Windows Management Instrumentation service.

If the above fails, you may need to reinstall WMI. To do this, use the following command:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

NOTE: This may require you to provide the Windows XP SP2 source media (either via CD-Rom or network share).

Error: "Can't communicate with the Server Group..."

Question/Issue:
When you unlock a server group in the Symantec System Center, you see the following error message: "Error: Can't communicate with the Server Group. Verify Network Connectivity and that machines are operating within the Group! If problem persists, try clearing the Server Group cache and re-discovering all Server Groups."

Refer URL:

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005051209365248?OpenDocument&src=ent_hot&dtype=corp&prod=Symantec%20AntiVirus%20Corporate%20Edition&ver=10.0&tpre=

Document ID: 2005051209365248

Moving Symantec Client Security 3.x or Symantec AntiVirus Corporate Edition 10.x clients from one parent server to another

Question/Issue:
You installed Symantec Client Security 3.x or Symantec AntiVirus Corporate Edition 10.x clients as a managed client of a Symantec AntiVirus server. You want to move one or more clients to a different parent server.


Solution:
Find your situation, and follow the directions.

To change the parent management server of a client manually when the servers are in the same server group

1. On the intended parent management server, copy the Grc.dat configuration file from the Symantec AntiVirus program folder.
   The default location on a Symantec AntiVirus Corporate Edition server is :\Program Files\SAV.
   The default location on a Symantec Client Security server is :\Program Files\SAV\Symantec AntiVirus.
   For directions, see the "To find the Symantec AntiVirus program folder" section in the Technical Information section of this document.
2. On the client computer, paste the Grc.dat file into the C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5 folder.
3. After a few minutes, the client finds the Grc.dat file in this folder, makes the appropriate changes to the registry, and then deletes the Grc.dat file.
   The next time that the client checks in with the parent server, the client will appear in Symantec System Center. You can force the check-in by editing the registry on the client computer.

To change the parent management server of a client manually when the servers are not in the same server group

1. On the intended parent management server, copy the Grc.dat configuration file from the Symantec AntiVirus program folder.
   The default location on a Symantec AntiVirus Corporate Edition server is :\Program Files\SAV.
   The default location on a Symantec Client Security server is :\Program Files\SAV\Symantec AntiVirus.
   For directions, see the directions in the "To find the Symantec AntiVirus program folder" section in the Technical Information section of this document.
2. On the client computer, paste the Grc.dat file into the C:\Documents and Settings\All Users\Application Data\Symantec\Symantec AntiVirus Corporate Edition\7.5 folder.
3. On the intended parent management server, open the pki\roots folder and copy the xxx.x.servergroupca.cer file.
4. On the client computer, paste the xxx.x.servergroupca.cer file into the pki\roots directory, which appears under the directory that contains the Symantec Client Security files.
5. After a few minutes, the client finds the Grc.dat file, makes the appropriate changes to the registry, and then deletes the Grc.dat file.
   The next time that the client checks in with the parent server, the client will appear in Symantec System Center. You can force the check-in by editing the registry on the client computer.

To force a client to check in with the parent server

1. On the client computer, start the Registry Editor.
2. In the left pane, go to the following registry key:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\LANDesk\VirusProtect6\CurrentVersion\ProductControl
   
   
3. In the right pane, double-click the ReloadRootCertsNow value.
   If the value does not exist, create it as a DWORD Value.
   
4. In the Value data box, press Backspace, and then type 1
5. Click OK.
6. In the right pane, double-click the ReStartPongEngineNow value.
   If the value does not exist, create it as a DWORD Value.
7. In the Value data box, press Backspace, and then type 1
8. Exit the Registry Editor.

Disabling the Firewall Using Group Policy

1. Create a new Group Policy object
2. Select the newly created group policy.
3. Right-click on the newly created policy and select Edit.
4. Expand the Computer Configuration folder, then the Administrative Templates folder.
5. Expand the Network folder, then the Network Connections folder, then the Windows Firewall folder.
6. Select the Standard Profile folder.
7. Double-click the Windows Firewall: Protect all network connections option.
8. Select Disabled, then click OK.
9. Select the Domain Profile folder.
10. Double-click the Windows Firewall: Protect all network connections option.
11. Select Disabled, then click OK.
12. Close the Group Policy dialog box.
13. In the Security Filter section, click Add.
14. Search for the objects that this group policy will be applied to, then click OK.
15. Close the Group Policy editor.

VMware View: Preparing a VM to be a linked clone master

Symptoms: Newly created virtual machine is not available to be selected during the pool creation wizard.

Resolution:
1. Configure VM OS as required in VC
2. Install latest View Agent
3. Power off VM
4. Right click VM > Snapshot > Take Snapshot
5. During the Automate pool creation wizard, select this snapshot as the Parent VM.

Passing arguments using VBScript

This code allows you to use a single VBScript for separate tasks by passing arguments e.g. SampleScript.vbs /task:argument01

Dim oArgs : oArgs = WScript.Arguments.Named.Item("task")

Select Case (oArgs)
Case "argument01"
WScript.Echo "Argument 1."
Case "argument02"
WScript.Echo "Argument 2."
Case Else
End Select