Tag Archives: Windows

First steps for troubleshooting Group Policy Errors

gpo

Group policy can be a bit of a pain to troubleshoot.
Here are a few pointers to get you going in the right direction when trying to fix errors:

  • Make sure you are running on a fast link. Preferably an Ethernet cable
  • Group policy might simply have not updated. At a command prompt run gpupdate /force
  • Running a Group Policy Results report can show you what policies have been applied. At a command prompt type gpresult /h path/to/file.html
  • Take a look at the event log to see if anything jumps out

Following these quick tips should get you on the right path to finding the problem.

Exchange Version and Build numbers to Service Packs

exchange-PowerShell

I was administering an Exchange 2007 installation today and needed to know what service pack it was running. The problem is that exchange does not display as a service pack, only an increase in version. A bit of googling revealed the following microsoft page that contains the version to Service pack information which i have duplicated at the bottom of this post for ease  http://support.microsoft.com/?kbid=158530

Find the Version of Exchange 2007

To find out the build number of Exchange 2007, launch an Exchange Management Shell and run the following command:

Get-ExchangeServer | fl name,edition,admindisplayversion
This will then give you the build number in the form of:

Name : EXCH01A
Edition : Standard
AdminDisplayVersion : Version 8.1 (Build 240.6)

Exchange Server Version lists 2003-2010

Microsoft Exchange Server 2003 6.5.6944 October 2003
Microsoft Exchange Server 2003 SP1 6.5.7226 May 2004
Microsoft Exchange Server 2003 SP2 6.5.7638 October 2005
Microsoft Exchange Server 2003 post-SP2 6.5.7653.33 March 2008
Microsoft Exchange Server 2003 post-SP2 6.5.7654.4 August 2008
Microsoft Exchange Server 2007 8.0.685.24 or 8.0.685.25 December 2006
Microsoft Exchange Server 2007 SP1 8.1.0240.006 November 2007
Microsoft Exchange Server 2007 SP2 8.2.0176.002 August 2009
Microsoft Exchange Server 2010 14.00.0639.021 October 2009

How to fix the “Could not connect to Group Policy Client service” Error

Recently a few of our Windows Vista machines have experienced a problem after removing Script Logic Desktop Authority from them, causing non-admin users to not be able to log into the machine.

GP-Client-service-error-large

The message that appears is
“Could not connect to Group Policy Client service. Please consult your system administrator.”
but strangely sometimes manifests as
“Windows could not connect to the system event notification service . Please consult your system administrator.”

After seeing this message, a normal user is dropped back to the Ctrl-Alt-Del logon screen.

This is how you can solve the problem if you are experiencing a similar problem

1. Log on to the machine as administrator
2. click start and into the search box type “Event Viewer” and press enter
3. Look in the Windows Logs under System for any Warnings or Errors. The error message will be something like Windows cannot process Group Policy Client Side Extension (Daci). Exception (in my case it was daci which is part of the script logic desktop authority program)
4. On the details tab, take a note of the GUID for the faulty client side extension
5. click start and into the search box type “regedit” and press enter
6. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions and then click on the string that represents your faulty GP Extension.
7. click on the file menu and choose export and save a backup of the file.
8. Once the registry is backed up you can delete the folder that corresponds to the GUID
9. Do a restart and log on as a normal user.

Problem solved!

How to fix McAfee VirusScan Corporate update error.

McAfee Update Issue – Affecting corporate users world wide

McAfee released an Anti Virus update early morning on Wednesday 21st April that falsely detects a core windows file, svchost.exe as a virus. It then quarantines or deletes the file causing windows to become essentially useless.

This problem seems to be only affecting Windows XP SP3 machines at the moment.

Some of the symptoms of the affected PC’s are:

  • Loss of Task Bar and Start Menu
  • Unable to connect to the network or internet

This has been a major problem for many companies as the current fix, at least right now, requires each machine to be touched by IT, in person, to repair the bad update as well as the svchost.exe file. As can be imagined, when faced with automatic updates across a company of hundreds or thousands of users, an IT department quickly has a major headache on their hands.

This is adding to the frustration and is causing delays resolving the problem.

If you are struck with this problem, and feel confident enough, you can fix this problem yourself, taking the strain off of your IT department and also getting yourself back up and running again.

Please note: Although straight forward, you will be accessing windows system files and as such due care and caution are advised. Please read through this guide thouroghly before attempting to perform this fix. If at any stage you are unsure, seek professional advice.

This guide has been adapted from the official McAfee Document – False positive detection of w32/wecorl.a in 5958 DAT (for Corporate/Business users) – VirusScan Enterprise found at http://vil.nai.com/vil/5958_false.htm

To fix the problem

What you need:

  • A working PC with internet access
  • A usb stick/pendrive

Step 1 – Download

  1. Then download the Updated DAT file which is available from the McAfee Security Updates page at: http://www.mcafee.com/apps/downloads/security_updates/dat.asp?region=us&segment=enterprise and save it to your USB Stick

Step 2 – Recovery

  1. Boot up the affected PC and insert the USB Stick
  2. Access Windows Task Manager by pressing Ctrl – Alt – Del on the keyboard
  3. From the File menu choose New Task (Run…)
  4. In the Create New Task box, Type explorer.exe and then press Enter
  5. This should bring up a windows explorer window that you can then use to navigate to the file system.
  6. Navigate to your USB Stick and double Click on the DAT update file that you downloaded earlier.
  7. Follow the instructions on screen to complete the update.
  8. Once complete, using the Windows Task Manager, once again from the File menu choose New Task (Run…)
  9. In the Create New Task box, Type “C:\program files\mcafee\virusscan enterprise\mcconsol.exe” /standalone and then press Enter
  10. This will bring up the management console for McAfee Virus Scan
  11. Double-click Quarantine Manager Policy, then click the Manager tab.
  12. Right-click the detection and select Restore.
  13. Restart your computer by using Windows Task Manager and from the file menu choosing Shutdown > Restart

That should get you up and running. If you are still having problems or would like someone else to do this for you, please get in touch