Archive for the ‘Win Srv 2003’ Category
Running SBS 2008 migration on a virtual server takes us on a detour down memory lane
Working on a migration of Windows Small Business Server (SBS) 2003 to SBS 2008, I had jumped thru the previous 283 migration hoops (I exaggerate, but just a little) and was ready to boot the 2008 installer DVD with my handy SBSAnswerFile which Microsoft wants me to put on “…the root of a USB drive, floppy disk or a partition on the destination server.” Hmmm….
– USB drive is a no-go on the ESX server.
– Let’s put it on a 2nd virtual hard disk. No, the migration installer didn’t “see” it.
– OK, let’s put it on a virtual CD drive. No. It didn’t see it again.
– Finally, I went to the extra hassle of putting it on a virtual floppy. Success!
The blow by blow follows:
Administration Tools Pack gets a refresh
Another eNerd called me yesterday wondering how to let a non-admin user at his client’s business have access to their virtualized server. The hope was to have the vSphere Client locked down in some way.
When I asked what the user needed to do, it was “Manage users and reset passwords and such.” I realized then that this was not a VMware access issue at all, but a Windows Server rights issue.
In fact, this can readily be handled by the Microsoft Management Console (MMC) which can be installed on the user’s workstation – no need to give the user login to the Windows or VMware server at all.
This is not a new trick by any means, but is one worth remembering.
Also, I’ll add that there is now a version for Windows 7 (Win7) and Vista, in both 32 and 64 bit flavors. (Sorry, they don’t let this run on “Home” editions of Windows.) The following give some details.
While installing Level Platforms (LPI) Onsite Manager onto a Windows Server 2003 (a member server running on as and ESXi guest and added to a SBS 2003 domain) all went well, but one service would not start. Final, solution was that the MWService account did not have sufficient permissions. LPI tech support said to add that account to Administrators, Domain Administrators and Enterprise Administrators. This solved the problem.
Read the rest of this entry »
Having set up my SBS server some time ago, I couldn’t remember where I had set the incoming port number (falsely called 65535 here.) I find the button that pops open the dialog box for this quite forgettable, so I’ll document this here hoping to help someone — me included — in the future.
Running TCPView from SysInternals shows that inetinfo.exe is listening on port 65535.
This was set in Exchange System Manager, drilling down seven levels to the SMTP-Default, right-clicking Properties, Advanced and editing the incoming port number. By default, this is port 25 for SMTP.
Some fellow Nerds were discussing the problem of Windows Updates having patches that refused to install, Nerds Todd Myles and Barry Ball suggested Dial-a-fix http://wiki.djlizard.net/Dial-a-fix.
I had been having the same issue with an install of Small Business Server 2003, so I decided to try this out. It worked quite well and took very little time. A great utility.
Below are the screen shots showing the blow-by-blow. Read the rest of this entry »
In this post, I tell how to detect if a Windows installation CD is bad using the CRC305.EXE.
Recently I again downloaded Microsoft’s Small Business Server 2003 CD ISO images and began burning them to CD on my laptop. To be sure they’re good, The MS download manager checks that the CRC values check. I have the Sonic software verify the CD after the burn to make sure it’s burned properly. Should be okay, right?
Ran through two complete installations of SBS only to find during and after CD #4 there are setup errors. The first indicates that a file for what appears to be a Korean help file just doesn’t exist. It’s one of two files, so I tried just copying and renaming the one file to be the name it wanted for the second file. I knew this was cheating, but what are the chances I’ll ever want help in Korean. It continues on until a final error indicates it cannot proceed. The errorlog.txt file showed numerous errors besides this one.
After re-burning CD 1 at a slower speed, I found I had the same error. I downloaded and ran CRC305.EXE from Microsoft’s web site and ran it against the CD on my laptop. It indicated that it was good. However, running it on the server on which I was trying to load the CDs indicated that ALL of the CDs had an error after the 99% point!
So I burned the CDs on THAT machine (yes there was a lot of time involved with this!), ran CRC205.EXE on that machine and it showed that the disks passed. I was able to install the complete system with the new CDs without errors.
For posterity sake, here are the screen shots for setting up client computers from an SBS server. I decided to include the initial user setup which provides for an automatic “next step” of setting up the computer. So there are two “push” parts: User setup and client computer setup and two “pull” parts: Assigning user to the computer / migrating their profiles and installing software via the Client Setup Wizard