Archive for June, 2007

WSUS 3.0 won’t install !!!

So you decided to finally bite the bullet and install wsus 3.0.  If you’re lucky (very lucky) it’ll install and migrate just fine.  HA!  There are lots of things that can go wrong.

If you’re on an older server that origianlly had SUS 1.0 on it, you probably won’t be so lucky.  WSUS 3.0 install will bark at you about still having SUS 1.0 installed!  But of course it isn’t.  What to do?  The answer lies in an obscure MS technet article that enumerates what WSUS 3.0 looks for before it installs.  Here’s the article: http://technet2.microsoft.com/windowsserver/en/library/2f276be4-f276-4bec-a565-c8757c6736b81033.mspx?mfr=true  Basically, the Key it is looking for is {AFF0D9D3-6F0D-437E-9327-98108B4A8644} in the HKLM/Software/microsoft/windows/current version/Uninstall key.  Find it and kill it.

 It should go without saying that you shouldn’t be trying to install anything else while you’re installing WSUS 3.0.  But you’re probably tempted to install the MS reporting Services Redistributable package while WSUS is doing it’s thing because you forgot it needed it (or didn’t know) and it barks at you that you need to install it.  Well, DON’T.  It’ll crash the WSUS install.

Permissions.  Sometimes WSUS 3.0 won’t have permissions to it’s own database.  Just like WSUS 2.0, the easy fix is to change the startup credentials of the update service to Local Admin instead of Network services.  This just in….the easy fix causes other problems - go figure.  If you had permissions problems in 2.0, your upgrade to 3.0 will probably fail with a 0×80070643 error.  Basically what is going on is it either can’t get at the database stored in WSUS because of permissions, or it can’t get at the new database in WsusDatabase because of permissions.  So, either fix the permissions on the root by adding Network services to it, fix the permissions on WSUS by adding Network Services/Full to it propogating it down to all sub folders and let the upgrade fail, then fix the permssions on WsusDatabase the same way and restart the upgrade pointing it at WsusDatabase, OR pre-create the WsusDatabase folder with the proper permissions and fix the permissions on WSUS before starting the upgrade.

Oh and don’t forget to download and install the Microsoft Report Viewer Redistributable 2005 thing before starting the upgrade.  You don’t have to, but it stops the complaining during the upgrade and you gotta do it eventually anyway.

Ok, so here’s the latest “gotcha”. Make sure the volume that you are putting the database on isn’t set to compress.  Or at least the folder it’s going to put it in.  If it is, WSUS 3.0 install will fail mysteriously.  But you read that it the realese notes didn’t you??? 

There’s probably more that can go wrong - I’ll add the fixes when I come accross them.

DS

No Comments


Enabling Password Change in OWA 2003

So why doesn’t Microsoft allow you to change your password in OWA?  Now that’s a very good question.  but Hey, it’s Microsoft - wadayaexpect?  anyway, here’s how to do it start to finish.  Including allowing users with expired passwords to change them.  Yep, that’s right there’s extra stuff to allow that.

I) Assuming you’ve already setup an SSL cert for the site… we need to setup a new virtual directory for the password change forms.

  1. Open Internet Information Services Manager from the Administrative Tools.
  2. In IIS Manager expand SERVERNAME (Where SERVERNAME is your server name object), expand Web Sites, and then expand Default Web Site.
  3. Right-click Default Web site and choose New, then select Virtual Directory.
  4. In the Welcome screen click Next.
  5. In the Virtual Directory Alias window type Iisadmpwd. Click Next.
  6. In the Website Content Directory screen navigate to %Systemroot%\System32\Inetsrv\Iisadmpwd. Click Next.
  7. In the Virtual Directory Access Permissions grant Read, Run Scripts and Execute permissions. Click Next.
  8. Click Finish.
  9. Change the Application Pool to ExchangeApplicationPool otherwise you’ll get permissions problems.
  10. See that the new Virtual Directory is listed in the folder list on the right-pane of the IIS Admin console.

II) Now we actually have to enable the change password button inside OWA.  You can do this with a registry hack but the best way, I think, is to download a little gem called OWAADMIN from MS.  Use this tool to not only to enable changing passwords, but you can putz with all sorts of other mildly useful OWA settings as well.  Oh, BTW, here’s the registry key just in case… KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeWEB\OWA - Create a new Dword DisablePassword and set it to 0.

III) Now, we need to fix the change the password when it’s already expired problem.  To do that, we need to download the IIS Resource Kit from MS and install it on the exchange server.  After the resource kit has been installed, run the utility called ‘Metabase Explorer’. This will open a ‘windows explorer’ type window that allows you to browse your IIS metabase configuration.In the tree in the left-hand window, find the ‘W3SVC’ entry, and select it in order to display the settings in the right-hand pain.Locate the setting ‘PasswordChangeFlags’ (You can alphabetize the list by name to make it easier to locate the setting)

If the setting is not ‘0’~
Double click on the ‘PasswordChangeFlags’ setting and change the value to ‘0’. (zero)

Close the IIS Metabase Explorer, and restart the web-site that contains the IISADMPWD virtual directory. (it should not be necessary to restart the WWW or IIS services, only the web-site).

IV) The last thing to do is to fix the Object requried error you get when you actually try to change the password when it’s already expired.  To do that we need to register a DLL that MS somehow forgot about.  

regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll

 

There, now wasn’t that easy???

No Comments


Older Autocads in Windows XP

Yep - yet another older program that needs a little bit of help to run in Windows XP without being a local Administrator.  To Get it to work right here’s what ya gotta do….

Grant the Users group Modify permissions to: C:\Program Files\AutoCAD LT98

For Autocad 2002 Modify the permissions on the following folder: C:\Program Files\Acadm 6

To fix the error: “This version of AutoCAD LT was not installed properly. You should reinstall AutoCAD LT immediately.” Open regedt32 and goto:

HKEY_LOCAL_MACHINE\Software\AutoDesk\

Click “Security - Permissions” then click the “Advanced” button. Double Click the line containing “Users - Read” and check “Set Value”, “Create Subkey”, and “Delete”.
________

To fix the error: “Failed to update the system registry. Please try using REGEDIT.” Open regedt32 and goto:

HKEY_CLASSES_ROOT\CLSID\{5E4405B0-5374-11CE-8E71-0020AF04B1D7}

Click “Security - Permissions” then click the “Advanced” button. Double Click the line containing “Users - Read” and check “Set Value”, “Create Subkey”, and “Delete”.

AND

HKEY_CLASSES_ROOT\AutoCADLT.Drawing.4

Click “Security - Permissions” then click the “Advanced” button. Double Click the line containing “Users - Read” and check “Set Value”, “Create Subkey”, and “Delete”.

Update: For Autocad 2002 modify permissions on the following registry keys…

HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk
HKEY_CLASSES_ROOT\AutoCAD.Drawing
HKEY_CLASSES_ROOT\AutoCAD.Drawing.15
HKEY_CLASSES_ROOT\CLSID\{8E75D913-3D21-11d2-85C4-080009A0C626}

ds

No Comments



SetPageWidth