If you are trying to deploy software within a Windows Business Environment you are most likely using a deployment solution like SCCM, PDQ Deploy or plain old Active Directory.
Whilst the deployment tools make things really easy for getting the software out to the masses, it does create a new trial (especially with SCCM) of finding the network deployable package with an MSI file being the Holy Grail
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
The time has come to set up our Windows Sharepoint Services installation to receive emails. One of the first things that you need to do is install the SMTP service on the sharepooint server using add/remove windows components.
So you go through the motions:
Click Start, Control Panel, Add or Remove Programs.
Click the Add/Remove Windows Components button.
Select the Application Server component and click Details.
Select the Internet Information Services (IIS) component and click Details.
Scroll down through the list and check the box next to SMTP Service, as shown in. Click OK, OK, and Next.
But instead of a nice and quick install you are presented with:
Setup cannot copy the file adsiiex.dll
No problem, just point the browser to your i386 folder on your win 2003 cd and all is well – Wrong! It’s not there!
You need to Extract the file from the cab file IMS.CAB and then point the browser to that file instead. The quickest way to do that is to fire up a command prompt and run the following command.
expand -F:* D:\I386\IMS.CAB C:\temp\ims
where D:\i386\IMS.CAB is the path to the CAB file and C:\temp\ims is a temp folder (which needs to exist before running the command)
This will solve your problem and allow you to complete your install of the SMTP Service
A bit late but still worth a post, Microsoft has announced (in April 2009) that Microsoft SharePoint Designer 2007 is now free!
Go over to SharePoint Designer 2007 Download to get your free copy.
For those who don’t know much about SharePoint Designer, here is an excerpt from Microsoft:
Build solutions faster to enhance team productivity and efficiency
Use Office SharePoint Designer 2007 to create and deploy interactive solutions on the SharePoint platform, without having to write code.
Automate business processes such as document approval, custom event notification, and other collaboration tasks with the Workflow Designer.
Create reporting and tracking applications using data views and forms to easily gather and aggregate data from outside your site and from SharePoint lists and document libraries on the Web site.
Get started fast with pre-built Microsoft Windows SharePoint Services Application Templates, which are fully customizable and extensible using Office SharePoint Designer 2007.
Extend your solutions by building advanced interactive Microsoft ASP.NET pages. Insert and edit controls with the same powerful activity menus and control property grid previously found only in development tools such as Microsoft Visual Studio 2005.
Well I got a new error today other day on one of our domain controllers after doing a restart. A bit of a bug in Windows 2003 SP1 and easy enough to fix. The error is:
Event Type: Warning
Event Source: MSDTC
Event Category: SVC
Event ID: 53258
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: %1
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I had this problem a about half a year ago where Outlook 2003 on terminal server would come up with a safe mode message for every user everytime they started it. At the time i solved the problem however a few weeks ago it came back and I couldn’t for the life of me remember how to fix it.
One of the uses of my blog is to document any bits of obscure IT related problems and their solutions so that if they happen to me again in the future i can just look up the solution without having to trawl google and waste time sifting through all the crap. Kinda like an IT helpdesk knowledgebase but for me.
So here goes:
When using Outlook 2003 on a Windows 2000 terminal server, you may receive the following error:
Outlook failed to start correctly last time. Starting Outlook in safe mode will help you correct or isolate a startup problem in order to successfully start the program. Some functionality may be disabled in this mode.
Do you want to start Outlook in safe mode?
No matter what you click Outlook opens – Yay.
No! The next time you launch Outlook you get the prompt again. And so on….
This is because when Outlook 2003 crashes or fails to load, the program generates this error message when you restart it. Safe Mode is a special operating mode that disables several of Outlook’s features but at least lets the program load so you can see existing emails and access other elements of the software.
What is happening here is that the program is not clearing the entry in the computer’s registry so it continues to display the error message.
To fix the problem you need to go into the registry on the server and do a search for “Resiliency” there will be quite a few entries (dependant on the number of terminal server users), you need to delete every entry that referrs to Outlook it should be something along the lines of: