scadblog

The other day I was trying to copy profiles from one Windows install to another.  One Windows install existed on an IDE drive, the other on a SATA.  I installed the two drives in the same machine and then proceeded to boot one of the installations in order to perform the file transfer.

Somewhere along the way the SATA drive, which would become the primary drive, had its letter renamed from C: to E:.  This created a problem as initial logins would crash explorer.exe, and subsequent logins failed entirely even after removing the secondary drive.

In order to restore the drive to its former glory, I booted from the IDE drive, loaded its SYSTEM registry key and looked in  the MountedDevices key.  There I found DOS\Devices\C: and DOS\Devices\E:, each with a GUID value.  I swapped the values, unloaded the SYSTEM key, rebooted to the SATA drive, and was able to log in; the SATA had been renamed C: and the IDE as E:.

The Toshiba Bluetooth Stack is software that can be found on Sony machines as well as Toshibas that ship with Bluetooth wireless adapters.  Pairing a device for something other than file transfer, in my case, ActiveSync, with the Toshiba Bluetooth Stack is counterintuitive and confusing, so here are the notes on the matter.  These assume you have ActiveSync installed.
1.  Set up a Server COM port via the Local COM Ports icon that the Toshiba Bluetooth Stack installs.

2.  Right click on the Bluetooth icon in the taskbar and click on Options.

3.  Under the Security tab click on Clustom Level and uncheck “Not Discoverable” and “New Authentication Denied” (yes, you read that correctly).

4.  Start ActiveSync and click on File and Connection Settings.  You want to make sure the Serial Port field has the COM port that you established in Step 1 selected.

4.   On the Windows Mobile handheld device click the Bluetooth icon.

5.  Under Devices click “New Partnership” and enter a random PIN number.  The computer will also request that you enter this random PIN at this time in order to create the partnership.

6.  Click the refresh button until you see ActiveSync listed as a service.  Make sure its checked off and then proceed to complete the pairing.

So I spent the better part of a week trapped in this scenario: the Sony Vaio VGN-SZ26CP/C, a Chinese market only model, was dropped in my lap with the request to put a clean install of the English version of Windows XP on it.

Anyone who has reinstalled Windows on a Vaio available in the US knows that it is not a pleasant experience due largely to the fact that devices will cease to function if the order of driver installation isn’t strictly adhered to.  In the case before me, I had no reference materials and only some of the necessary drivers kindly left at the root level of the C drive.

After days of trial and error I finally emerged with a fully functional Vaio.  In summary the process involves extracting the drivers from the factory install via a third party utility, requesting a special patch from Microsoft, restoring some of the extracted drivers in a particular order, then using the original driver installers for a similar US model via the Sony support site to take care of the remaining troublesome hardware.

Please note that when an actual installer is indicated for US model VGN-SZ260P in the steps below it is meant to be the original installer that shipped with the machine. An updated installer checks the make and model of the machine and will prevent an installation.

1. Extract the drivers from the original factory installation (I used Driver Magician).
2. Install the extracted Intel Chipset.
3. Request KB909667 from Microsoft and apply it.
4. Install the extracted Sony Notebook Control driver.
5. Install the extracted Sony Programmable I/O driver.
6. Install the Sony Shared Library for US model VGN-SZ260P.
7. Install the Sony Notebook Utilities for US model VGN-SZ260P.

At this point you should have the Vaio-specific keyboard functions working.

8.  Install the SigmaTel Audio driver for US model VGN-SZ260P.
9.  Install the HDAUDIO Modem driver for the US model VGN-SZ260P.
Your audio should technically be working.  I had to repeat steps 8-9 multiple times both before and after 10-11, but eventually the sound came to life.

10.  Install the Bluetooth Stack for the US model VGN-SZ260P.
11.  Install the Bluetooth Control driver for the US model VGN-SZ260P.

After installation of Bluetooth, the remaining drivers should install individually without issue.

These are the notes for creation and customization of a Windows XP 64-bit image exclusively for Operations Research & Financial Engineering. The notes are updated as I change the software set and configuration options. Software is 64-bit bit unless otherwise noted.
(more…)

OIT’s dedicated Kerberos server is no longer included in the list machines where new faculty, staff and students receive accounts upon their initial Princeton account creation. This presented a problem for me earlier this year as I had been authenticating against it and the realm PRINCETON.EDU for some of my Linux users.

The Windows Domain Controllers are also technically Kerberos, so I set out to authenticate against it in a similar manner. Here’s how its done on CentOS, but the only thing that should differ if using another distribution is how your PAM configuration is organized and split up among the config files.

/etc/krb5.conf
[logging]
default = FILE10000:/var/log/krb5lib.log

[libdefaults]
ticket_lifetime = 24000
default_realm = PU.WIN.PRINCETON.EDU
default_tkt_enctypes = des3-hmac-sha1 des-cbc-crc
default_tgs_enctypes = des3-hmac-sha1 des-cbc-crc
[realms]
PU.WIN.PRINCETON.EDU = {
kdc = pdom1.pu.win.princeton.edu
}
[domain_realm]
.princeton.edu = PU.WIN.PRINCETON.EDU
princeton.edu = PU.WIN.PRINCETON.EDU

/etc/pam.d/system-authauth

required /lib/security/$ISA/pam_env.so
auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok
auth sufficient /lib/security/$ISA/pam_krb5.so use_first_pass
auth required /lib/security/$ISA/pam_deny.so

account required /lib/security/$ISA/pam_unix.so broken_shadow
account sufficient /lib/security/$ISA/pam_succeed_if.so uid < 100 quiet
account [default=bad success=ok user_unknown=ignore] /lib/security/$IS/pam_krb5.so
account required /lib/security/$ISA/pam_permit.so

password requisite /lib/security/$ISA/pam_cracklib.so retry=3
password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5 shadow
password sufficient /lib/security/$ISA/pam_krb5.so use_authtok
password required /lib/security/$ISA/pam_deny.so

session required /lib/security/$ISA/pam_limits.so
session required /lib/security/$ISA/pam_unix.so
session optional /lib/security/$ISA/pam_krb5.so

Why has it taken me the entire life span of Windows XP to even think to look for this?  This has been on O’Reilly since 2004.  This is incredibly handy when you have to work on a machine locally as administrator but the user is nowhere in sight.  Now I just have to find out how to script the part where it says to use the Task Manager to disconnect the user.  That’s annoying.
“Disable Welcome Screen& Fast User Switching via Control Panel > User Accounts. Manually edit the registry and set AllowMultipleTSSessions=dword:0000001

Now, “Disconnect” the current user using Task Manager > Users tab.

Type in the login name in the Classic Logon dialog and login as other user.

P.S: The Winkey+L cannot be used in this case to switch users. The only option is thru Taskmgr. Winkey+L still brings up the Classic Logon dialog, but terminates the current session, unlike the Task Manager method.”

The Tiger Card office handles all requests to OIT for PU NetID creation and all that that entails.  This usually takes place within a 24 hour window based on what I can only assume is start or appointment date for the individual.  In my case I needed to find this out for a guest appointment, but I suspect that the accounts for faculty and graduate students are created on different schedules; I’ve seen them months in advance.