I'm on my second Macbook. My first one was fast and beautiful but it had that annoying moo and randomly shut down on a regular basis. For reasons unknown, an AppleCare rep told me on my 5th call that my laptop was DOA and could be exchanged for a new one. It was well past my 14-day exchange limit and I found it so hard to believe, I asked him/her to note it on my profile. It took about 3 weeks for me to find the time to back it up, wipe it and schedule an appt with a Mac Genius. I get there after wiping my drive (as instructed) and the rep told me that I was given the wrong information -- I could only repair my laptop, not exchange it. I was liek omg, check my profile, plz. Long story short, they honored the inaccurate information because it was noted (so always ask for it in writing!)
(more...)
I'll have a more complete list later, but here is the order the network admins at work have figured out works best when using the Active Directory Migration tool to migrate from NT 4 to Server 2003 (be sure to check the rest of the blog for other scripts which are necessary when using ADMT):
1. User with SID (/Groups with SIDs)
2. Machine
3. Security Translation Wizard
We are currently bringing over groups, along with their SIDs, during the User migration. This allows us to filter out old groups that once had a purpose but no longer have members. Since ADMT does not migrate or translate the SID for built-in groups, we used sidhist.vbs, a file available in the Windows Server 2003 Support Tools.
cscript sidhist.vbs "/srcsam:Domain Users" "/dstsam:Domain Users" /srcdom:ourOldDomain /dstdom:ourNewDomain /srcdc:anOldDC /dstdc:aNewDC
When we ran it in the order Machine -> User -> Security Translation Wizard, the users' profiles (Desktops, Outlook, etc) were not migrated. We thought we'd have to resort to using Windows User State Migration Tool (USMT) but thankfully, this was no longer necessary once the correct migration order was discovered. Thanks to Jerf & Neddles for sharing this info!
For years I've used Windows Server 2003 and for years, I've been missing some of my favorite features from Windows Powertoys. The Image Resizer Powertoy is definitely one that came in really handy when I used XP. Unfortunately, anytime I tried to run it under 2k3, I would receive the message
The powertoys require Windows XP or a service pack. They will not function on a version of WIndows ealrier or later than Windows XP
Recently, when trying to extract MacBook drivers, I learned about InstallShield's "/V /a" switch and I decided to try it on ImageResizerPowertoySetup.exe. I downloaded the file from the Microsoft PowerToys for Windows XP webpage and saved it to my D: drive. I then ran D:\ImageResizerPowertoySetup.exe /V /a and extracted the contents to D:\temp. I saw that a folder called "system32" was created. I then moved the file phototoys.dll to C:\windows\system32 then went to Start -> Run -> regsvr32 phototoys.dll. Voila! "Resize Pictures" appeared in my right-click menu.
I assume that this technique will work for all or most other XP PowerToys.