This is an interesting one that i came across recently whilst trying to deploy an image to a brand new Microsoft Surface Pro 3.
I had two sitting on the bench ready to deploy our stock Windows 8.1 image. The first Surface PXE booted fine and jumped straight into the task sequence as normal however the second one came up with an error 0x80004005 when trying to look for the task sequences.
I knew that it wasn’t the image as surface numberone was working fine. I checked all of the usual things, replaced the ethernet cable etc and after a few reboots, I still had the same error.
After a little digging I found the solution.
The time in the UEFI BIOS was wrong.
The problem is that there is no option to change the time in the UEFI BIOS so you must change it using the PE environment instead:
Make sure that your boot image has command support enabled.
Boot into the Config Manager image.
Before proceeding any further, press the F8 key (Fn + F8).
At the command prompt type the ‘time’ command to change the current time.
Next type the ‘date’ command and enter the correct date following the format for the locale of the PE.
Verify that it has applied by typing
Close the command prompt and continue with your build.
When trying to access outlook web access on SBS 2011 by going to https://yourserver/owa. You see the login prompt but after entering your credentials, you are faced with a blank page with https://yourserver/owa/auth.owa in the address bar.
This is normally due to the Forms based authentication service not running. Sometimes it fails to start when a PC restarts.
To resolve the issue:
Start the Microsoft Exchange Forms-Based Authentication Service
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.
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.
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