Quick one – if you get the below error when doing a “repadmin /showreps”;
Make sure you are running Command as an Administrator!
Had the following a few times now – Outlook Anywhere not working for Exchange 2010 SP1 when the Authentication method is set to Negotiate.
Event logs show the following;
Process ID: 5200
Process name: w3wp.exe
Account name: IIS APPPOOL\DefaultAppPool
Exception type: ConfigurationErrorsException
Exception message: Could not load file or assembly ‘WindowsLiveID, Version=0.0.0.0, Culture=neutral, PublicKeyToken=283dd9fa4b2406c5’ or one of its dependencies. The system cannot find the file specified.
In short, change from Negotiate to NTLM as Negotiate introduces the WindowsLiveID provider, and this causes Outlook to fail authentication (in short).
If NTLM is already enabled (or Basic) then make sure that the WindowsLiveID provider isn’t being inherited (look in IIS Manager under /RCP in the “Modules” bit
Found a fab script the other day for installing the pre-requisites for Lync – its all menu driven and allows you to get the right pre-reqs for the Role/s required;
Bluescreen when saving to Shares with symbolic links (wide links) on a NetApp with Kaspersky installed
Phew, what a title!
Had a customer recently who I was working with on doing a Netware –> NetApp CIFS migration utilising the Quest NDS tools.
All was working fine until one unlucky user attempted a save to a “Volume” share, they received a BSOD (repeatedly if they attempted again).
Now, to explain the NetApp CIFS configuration a little before ploughing on;
There are three shares created on the new NetApp;
VOL1 contains symbolic links (wide links) to SHARE1 and SHARE2 to allow historic applications looking for \\SERVER\VOL1\SHARE1\FILE1.EXT to function.
The customer was also mid-AV upgrade – from McAfee to Kaspersky.
When a Kaspersky-running client attempted to save (via Office for example) they received a BSOD with the header RDR_FILE_SYSTEM (27). A Bug check analysis didn’t give me any more info (aside from an “Access Violation” error further down).
Testing was done with different XP SP/Office levels before we turned to the AV – and sure enough it looked to be Kaspersky.
Kaspersky replied to the support email sent very promptly – outlining this was a known bug in XP/2003 but Microsoft had only released a patch for Server 2003. However they had their own patch – which seemed to resolve the issue. I believe it to be a private release patch at the moment – however they have said it will be written into the next point release
Hope that helps someone anyway
Long time no see y’all – been a bit quiet but am back with another bug from Microsoft;
When attempting to close MMC (Active Directory Users and Computers or the Exchange Management Console for example) on a Windows 2008 R2 server with Internet Explorer 9 installed you get the following error;
For the sake of our friend Google (as I’m not using my normal software to fill out the “blanks”) – thats “You must close all dialog boxes before you can close Exchange Management Console”
There is an interesting thread on the Technet forums that has been going some time;
It looks to affect Windows 7 also – so it must be the “7” suite of OS’s (i.e Windows 6.1).
The “work-around” at this moment is to uninstall IE9 – which is fine on your server (and not so fine on your Desktop). Some users have reported that disabling Enhanced Security for IE is a temporary fix (along with adding http://localhost and https://localhost to the Trusted sites), though I don’t see how this would work with Windows 7.
Official line from MS at this moment is “Sorry, we are working on it”.
Funnily enough it only seems to happen when certain dialog boxes / panes are opened (see above Technet post) – so if you do get it just kil mmc.exe from the Task Manager 🙂
The Quest pre-requisites for GroupWise to Exchange migration (for Exchange 2010) has the following command;
Also: Depending on your environment, you may need to run this command to enable the
PowerShell layer using remote PowerShell:
|get-executionpolicy | set-executionpolicy unrestricted|
This is incorrect on Windows XP SP3 (PowerShell 2) and should be;
Recently deploying a 2008 R2 print server to server printers out to Windows XP (x86) clients.
When I came to install the first x86 driver, it complained that it required a x86 version of ntprint.inf (please provide a path to windows media x86). This is obviously not to be found on a 2008 R2 x64 system, so I did a bit of digging.
Lots of Technet posts later, and I came up with the following post;
STEP BY STEP GUIDE TO GET A WORKING NTPRINT FOLDER FROM WINDOWS 7 MEDIA.
If you have a Windows 7 32-bit CD, perhaps with a new computer, OEM disc should work fine, do the following:
1. Make a folder on your C Drive called Win7Mount
2. Obtain a copy of ImageX. This can be downloaded from Microsoft. It is their new imaging software.
3. Insert your Windows 7 DVD or mount your ISO. Note the drive letter.
4. Open a command prompt and change directories to wherever ImageX is installed. I have the Windows AIK installed so mine was at C:\Program Files\AIK\Tools\x86.
5. Type the following command: imagex /mount H:\Sources\install.wim 1 C:\Win7Mount and press ENTER.
6. Wait for imagex to complete. Will take 2-3 minutes to fully mount DVD.
7. Now browse to C:\Win7Mount\Windows\winsxs\
8. Copy the contents of x86_ntprint.inf_31bfxxxxxxxxxxxxxxxxxxxxxxx to wherever you save your Print Drivers. I called it "Windows 7 32-bit NTPRINT". That way when I need it in the future I will remember what it was for. (Note: there is another folder called x86_ntprint.inf.resources_xxxxxxxxxxxxxxxxxx. I copied the contents of that one as well, but didn’t need it. I figured I might in the future so I went ahead and grabbed it now.)
9. Now type: imagex /unmount C:\Win7Mount and press ENTER. This process will take 60 seconds or so.
10. Now when the print server asks for the Windows media, just browse to that new folder you created and it will find the files needed.
However this gave me a “the system cannot find the file specified” when running step 5. Hmm time to do some more digging.
After some more prudent digging I decided to use DISM to mount the image, so here is some updated instructions! 🙂
1. Make a folder on your C Drive called Mount
2. Insert your Windows 7 DVD or mount your ISO, or extract the contents using something similar to WinRAR. Note the drive letter/or location of extraction
3. Open an administrative command prompt.
4. Type the following command “dism /mount-wim /WimFile:d:\install.wim /index:1 /mountDir:c:\mount” and press ENTER.
5. Wait for dism to complete. Will take 2-3 minutes to fully mount DVD.
6. Now browse to C:\Win7Mount\Windows\winsxs\
7. Copy the contents of x86_ntprint.inf_31bfxxxxxxxxxxxxxxxxxxxxxxx to somewhere sensible.
8. Now type: “dism /unmount-wim /mountdir:c:\mount /discard” (where c:\mount is your mounted dir) and press ENTER. This process will take 60 seconds or so.
9. Now when the print server asks for the Windows media, just browse to that new folder you created and it will find the files needed.