VLite, Windows Activation, SLUI.exe, and SCARDDLG.DLL

Fun times.

I vlited Vista a while back when SP1 was released. I cropped almost 3GB worth of Vista DVD into 900MB worth of awesome install. It fit on two CDs. I liked it.

Fast forward to today – SP2 for vista was released a couple days ago to MSDN/partners. I download the rather large install and attempt to update my system. Fail. Epic. Apparently I’m “missing” key components needed by the SP2 installer. So I’m stuck on 1. Yippie.

So I go ahead and download the whole schebang – Vista Enterprise SP2. Then I go ahead and vlite this installation – but I only manage to cut the installer in half – 1.58GB out of the original 2.98GB. Four CD’s later I’m in business; burned and ready to install.

Installed without any issues, and it’s not even complaining. Seems faster already too.

ANYway, I attempt to run the Activation for windows. ERROR! ERROR! ERROR!

slui.exe – System Error

The program can’t start because SCARDDLG.dll is missing from your computer. Try reinstalling the program to fix this problem

Well that sucks. How am I supposed to activate this beast? I check on the original DVD to see if the dll is floating around – no dice. I check on another vista machine (SP1) – no dice. So then I remember that post CAB file days, Microsoft has files known as WIMs. AND since I needed to install that 1.3GB AIK microsoft installer for vlite to run, I already had the tool required to view said WIM files.

Grab the original Vista SP2 Disk and put it in your Optical drive (Or Daemon Tools virtual mount the ISO)
Create a directory called “vistamount” on your C:\ drive
Start -> All Programs -> Microsoft Windows AIK -> Windows PE Tools Command Prompt

imagex /mount f:\sources\install.wim 1 c:\vistamount

Now you’ll be able to navigate to c:\vistamount\windows\system32\scarddlg.dll. Throw this file into c:\windows\system32 and then try to reactivate.

sdra64.exe

I was recently given a laptop that refused to cooperate with the end user. Safemode only worked half the time, and regular boots would just hang after attempting to login.

The computer ended up having a windows init known as sdra64.exe. I don’t even care what these programs do anymore – I just get rid of them.

Quick google search provided me with this guy’s blog:
http://mrmusicmaker.blogspot.com/2009/04/how-to-remove-sdra64exe-yourself-for.html
Although I’m going to provide a different way to fix this issue, a lot of the knowledge was gained from the above blog about this problem and how to fix it.

First, grab your handy IT-Fix-It Disc (Hirens).
Boot off the hirens disc – I’m using version 9.8, current at the time of this writing
Boot into Tiny/Mini XP
After XP loads, open My Computer and navigate to C:\windows\system32\
Find the file sdra64.exe and either delete or rename this file. I renamed just in case I really wanted to go back to the way it was.
Then reboot back into safe mode (F8 before Windows starts loading).

When in safe mode, open the registry Start
Run
Regedit
Navigate to
HKLM\software\microsoft\windows nt\currentversion\winlogon
Find the “userinit” key
Double click on this key
You should only have the following:
C:\Windows\System32\Userinit.exe,
So delete anything after that comma.

Reboot once again, but this time don’t go into safe mode. You probably will have other infections that you should remove using Malwarebytes or Eset’s Nod32. Combination attacks work the best.

Exchange 2007 Full Mailbox Rights

In case you haven’t noticed, Microsoft took a giant leap backwards from their AD management of Exchange. It’s now back to the way it was Pre-2000 (5.5 anyone?) instead of 2000/2003 ish. One of the nice things about 07 is that they gave us a command line interface that is actually pretty nice (once you get the hang of how it all works).
This is how to setup a user with full mailbox rights – you can also choose other options instead of FullAccess.
This also assumes that you know the login/mailbox of the user you want to give permissions to as well as the user you want to take the permissions from.

Open up the Exchange Management Tools
Add-MailboxPermission OF_USER -User TO_USER -AccessRights FullAccess

So in my case it was:
Add-MailboxPermission computeruser -User computeradmin -AccessRights FullAccess
Which gave the computeradmin full access to use the computeruser’s mailbox.

3 Three Tres Drei

I just realized that I’ve been posting for Three years running. That’s a long time.

And I’m only sure that a couple of these posts were really helpful – but they probably all helped me at one time or another.

Anywho, Just thought I’d point out the 3 year anniversary. To me. Yippie!

Windows Update not Windows Updating

I’ve had this issue more often than I’d like to actually care to remember.

First thing I check is website security settings:

Open IE
Select Tools
Select Internet Options
Click on the Security Tab
Click on the Trusted Sites button (check mark)
Click on the Sites button
Add https://update.microsoft.com, http://update.microsoft.com, and any other microsoft update related sites

Next thing I generally check is if the Trusted Sites are actually being trusted

Open IE
Select Tools
Select Internet Options
Click on the Security Tab
Click on the Trusted Sites button (check mark)
Click on the Custom Level button
Make sure that the security is at Medium or below (Medium, Medium Low, or Low) – I generally put this at Low

After that make sure that the following services are enabled:

Start
Run

services.msc

Automatic Updates/Background Intelligent Transfer Service (BITS)

Finally, if nothing else works, turn off Automatic Updates and remove the SoftwareDistribution folder

Start
Run

services.msc

Right-Click on Automatic Updates and select Stop
Start
Run

%windir%\SoftwareDistribution

Open the DataStore folder
Delete everything inside
Right-Click on Automatic Updates and select Start
Retry the Windows Update

Install VMWare Server 2.* on Debian 5.0 Lenny

I started with an HP DL380 G4 – dual 3.4GHz Xeon single core 533MHz bus, 4GB RAM, 6x 36.4GB SCSI in RAID5 (182GB available), 2U server. I then went on to install Debian 5.0 Server x32. If I ever want to run Wine or another program it’s generally still easier to run 32bit software. That and I only have 4GB RAM anyway.

So then I wanted to install VMWare Server 2.0.1 for Linux. The exact file name and version: 2.0.1-156745.i386.tar.gz. Why not ESXi? While ESXi is also free and a hyperadvisor, there seems to be a lot more overhead in terms of administration and setup – that and I can’t figure out how to speed up the transfer of virtual machines over the network. AND we already have several other servers running VMWare Server so we can still use the linux side for internal sites.

I knew it would be a challenge so I was ready for whatever I needed to do. Running this same setup on CentOS took less than half the time. However, CentOS has a much larger footprint and takes noticeably longer to install. And now that I have the steps required, I think I shall use Debian more often. Apt-get > Yum. Nano > vi.

I’m assuming that you have a fully installed Debian server here and you have at least a little knowledge of linux. Most of the steps do not require me to let you know what’s going on. I always run the install as the root user (su), so you can add sudo to all the commands if you so desire.

I’m also assuming that you went to www.vmware.com, clicked on Products, then on Server (Free). You’ll have to sign up for an account before you can download, but that’s easy enough. Download the appropriate file, in my case it’s 2.0.1 32bit linux server NON-RPM.

First gunzip and de-tar our file:
tar xzvf VMware-server-2.0.1-156745.i386.tar.gz
cd vmware-server-distrib

Then we need to grab the prerequisites:
apt-get install libx11-6 libx11-dev libxtst6 xinetd wget
Notice that these are NOT quotes or apostrophes. Very important step BTW.
apt-get install linux-headers-`uname -r` build-essential
apt-get install binutils-doc make manpages-dev autoconf automake1.9 libtool flex bison gdb
apt-get install gcc
This will remove a “setup is unable to find the ‘killall’ program” error.
apt-get install psmisc

Might as well do some housecleaning and make sure everything is up to date.
apt-get update
apt-get upgrade

Now you can run the installer:
./vmware-install.pl

If the installer complains about the gcc kernel version:

Your kernel was built with “gcc” version “4.1.3”, while you are trying to use “/usr/bin/gcc” version “4.3.2”. This configuration is not recommended and VMware Server may crash if you’ll continue.

Blah blah blah.

First, show all the installed versions of GCC:
ls -l /usr/bin/gcc*

Which spits out the following:

lrwxrwxrwx 1 root root 7 2009-05-06 09:17 /usr/bin/gcc -> gcc-4.3
-rwxr-xr-x 1 root root 196996 2009-01-18 09:39 /usr/bin/gcc-4.1
-rwxr-xr-x 1 root root 207648 2008-12-31 06:52 /usr/bin/gcc-4.3
-rwxr-xr-x 1 root root 16288 2009-01-18 09:37 /usr/bin/gccbug-4.1

You can see that the gcc command is linked to version 4.3. Let’s link it back to 4.1 so vmware can stop complaining.
su -
export CC=/usr/bin/gcc-4.1
Then rerun vmware-config.pl

You will see that the compiler will now use GCC 4.1, which just so happens to be the same version that was used to compile the kernel. No more complaints! Yay!

Basically follow the wizard the remaining steps and you should be fine. The above should save you quite a bit of time, frustration, and … if you’re a consultant it’ll make you look good.

https://IP_OF_SERVER:8333/ui will then allow you to login using the information provided during setup of the server/setup of VMWare.