SBS - SysInternals BGInfo Quick Config

Every server install that we do, whether SBS, Windows Server 2003, or others, we always copy the BGInfo - Background Info - utility into the Startup folder on the server.

The utility can be obtained here: Systernals BGInfo.

A screen shot of the background from the SysInternal's site:


Also from the SysInternal's Web site, a screen shot of the default settings in the utility:


This is the standard background configuration we use:

Host Name: <>

Boot Time: <>
Snapshot Time: <>

CPU: <>
Default Gateway: <>
DNS Server: <>
IE Version: <>
IP Address: <>
Logon Domain: <>
Logon Server: <>
Machine Domain: <>
Memory: <>
Network Card: <>
Network Speed: <>
OS Version: <>
Service Pack: <>
System Type: <>

Volumes: <>
Free Space: <>

The Blogger interface is really having a hard time with the greater than and less than symbols. It keeps wiping out the data in them, or not showing them at all. The latter is due to the software assuming that whatever is within the symbols is code.

There should be no space between the symbols and the data field.

So, when we have a moment, we will post a zipped text file of the configuration. It is nice to have access to when we setup new site servers.

Update: They showed up in the post, so you can copy and paste them into a text document as well and remove the spaces!

UPDATE: Here is a link to the text file: BGInfo Settings (zip file).

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Fax and modems - USB or Serial?

Lately, we have been in a bit of a quandary. Pretty much all server boards no longer have PCI slots to install that 56K fax modem into anymore.

So, we started selling the US Robotics USB based external: 56K* USB Fax Modem:


All in all, we have had pretty good success with these units. There have been some anomalies with them that we haven't been able to pin down 100%. But, we are pretty sure they are the culprit. The anomalies are not critical in that they don't spontaneously reboot the server or interfere with critical server services. They are minor inconveniences.

One thing we like about them, they tolerate having other fax machines, such as MFPs, on the same line that are only used to send faxes from.

In some cases, we have installed the US Robotics USR5686E, USR325686E 56K V.92 External Faxmodem:


These serial based modems have worked well where the phone line quality is not so good. They do however, have an issue with any other fax machine trying to send a fax on the same line. They like to pickup and try and receive. So, they need to be on their own line for receiving faxes. They are that sensitive.

What are your experiences? What modems do you use, and how well are they working out for you? Have you had any issues with USB modems?

Please, let us know and thanks in advance! :D

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Top Ten (Plus One) Myths about Windows Small Business Server 2003

We came across this Microsoft site: The Top Ten (Plus One) Myths About Windows Small Business Server 2003.

Here are the myths in a nutshell:

1. I cannot add additional servers to a Windows SBS domain.
2. I cannot run Terminal Services in the Windows SBS domain.
3. Windows SBS doesn't scale.
4. Windows SBS requires different hardware than Microsoft Windows Server 2003.
5. I cannot upgrade my current server.
6. I'm going to outgrow Windows SBS.
7. The Exchange Server 2003 mail store limit is too small.
8. My applications are not supported on Windows SBS.
9. Windows SBS has scaled-down versions of applications.
10. I can't use the tools from Windows Server 2003 in Windows SBS.
11. Windows SBS isn't secure.

For those of us who design, implement, service, and support network infrastructure around SBS, we know these myths are a load of bunk.

If anything, it is a good 5 minute read to refresh and/or inform us of what SBS is not.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows Vista - USB Reliability Stack Update Required

Keep in mind that any Bluetooth enabled Microsoft Hardware product carries the following in the product box:

Critical Update Warning

One needs to go to the Microsoft Hardware site via the link indicated: Update for Windows Vista.

The link brings you to:


Note that the update applies to both the 32bit and 64bit versions of Windows Vista.

This is a pair of updates that one should keep on their technician's memory stick for those just-in-case moments where there may be no Internet access or site restrictions.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows Vista x64 - Adobe Acrobat 8 Professional "Printer" not Generating PDFs

Out of the box, we had a couple of issues with installing Adobe Acrobat 8 Professional (previous blog post).

So, we have not been able to use the product to generate PDFs via the built-in printer AdobePDF setup.

When trying to diagnose what was going on we went into the Adobe Printing Preferences. Initially the "Adobe PDF Folder" was blank. When clicking the down arrow for any options, the only one available was LPT1:.

So, we selected LPT1:

Adobe PDF Printing Preferences & Properties

Click the General tab in Adobe PDF Properties, click on the Print Test Page button, and bingo! We have a standard Windows Printer Test Page that indicates we have correctly installed our Adobe PDF Converter.

Well, the next step was to figure out how to get it to prompt us to save the PDF in a directory.

We have another system setup with Acrobat Pro running on Windows XP Professional, so we took a look:

Adobe PDF Properties on XP Pro

So, on our Windows Vista x64 Adobe Acrobat Professional 8 did not setup those ports.

From Adobe's support site: TechNote: Error "Warning 20225..." or no Adobe PDF printer appears (Acrobat 8.0 and Acrobat 3D 8.0 on Windows).

Acrobat is not supported on a 64-bit operating system [emphasis ours]. Acrobat 8 should be able to install the printer but not the Adobe PDF port on the 64-bit operating systems; although, the remainder of Acrobat functionality should remain intact. In addition, Acrobat is unable to install the printer if extended ASCII or double-byte characters are found in the path names. Third-party programs can interfere with the installation of the printer by attaching services to the Print Spooler service or installing print monitor software. Lexmark and Dell printers are known to install services such as lexbce.exe that can generate this error message.

There is not Detect and Repair on our help menu either.

Some things are just to goofy...click "Check for Updates" and the first thing it does is download 168MB of updates.

The first one it installs is on Acrobat, so after the update is done, guess what:

Adobe PDF Port is now available

Adobe, you have great timing! :D The Help --> Repair Acrobate Acrobat Installation menu item is there too.

Some further links:

• Adobe's statement on Windows x64 support: Support policy for Adobe Acrobat 8.0.x Windows x64.
• Adobe Forum thread: Support for Windows 64 bit.

Kudos to Adobe for bringing about an update to support those of us who have paid the big bucks for their products.

It is good to see!

UPDATE 2007-09-25: Okay, my bad ... It is Acrobat not Acrobate! :D

UPDATE 2008-08-26: As per the comments:

1. In the Printer list delete the Adobe PDF printer
2. In Acrobat run the repair routine.

Once the repair has run, you may need to update your Acrobat installation to the newest revision.

That works.

Thanks to those who commented for contributing a fix! :)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows XP/Vista - Configuring a Static Route

There are occasions where we may need to have a static route configured on a Windows desktop operating system.

With a server, it is no big deal as we configure it in RRAS.

But, with the desktop operating system, we need to work at the command line with the route command.

• Windows XP: Route Command.
• Windows Vista: Configuring Multiple Gateways.

Note that on Windows Vista for IPv6 one needs to use the netsh command to set the routes.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows Vista x64 - Some Observations

There have been some interesting pluses to installing the 64 bit version of Vista.

One is the full 4GB of RAM on the system is now utilized. Another, and this could be purely subjective as we haven't run any actual tests yet, is that the system seems to run faster - way faster. Photoshop just opened for the first time in a couple of seconds. It definitely did not do that previously.

After booting, the system settles in around 2-2.5GB of RAM allocated. Keep in mind that this particular system has a lot of TSRs on it. This is a screen shot with several browsers and Outlook open in the background:


That resource metre is always kept open on the desktop. It is a bird's eye view of what is happening on the system at any given time, and is a good indicator as to an application's ability to utilize all four cores on this system.

Even Outlook 2007 doesn't seem to stall as much as it did before. There is still some waiting for some emails to open when clicked on, but no where near as bad as the "go get a tea and come back" waiting that it was before when running on XP Pro 32bit.

There are some issues with third party software though:

• To install Adobe Acrobat 8 Professional, one must extract the AdobePDF.dll_64 from the data.cab to the desktop and name it AdobePDF.dll when the install chokes and asks for the AdobePDF.dll from the "Windows Vista CD-ROM"!
• The Adobe PDF "printer" does not work as it should for creating PDF documents from applications. From IE, it just hangs IE and the Spooler. From an application like Word the print job flashes through the print manager with no dialogue to save the newly created PDF.
• Chapura's PocketMirror Professional for Windows Mobile is not compatible with Vista x64 despite the "Now Supports Windows Vista" logo on their site.
• The Creative X-Fi drivers did not setup properly the first go around. The noise that came from the speakers was unbearable. After one day of the system being on though, Vista popped up the "Problem with" dialogue that had the Creative driver site link in it to "resolve" the problem. Funny thing though, since that dialogue box came up the sound has been working fine!

IMNSHO, this operating system ROCKS! :D

Why do I say that? Because there are two people in my life who are examples of typical Windows users: My wife Monique and my Dad. We transitioned to Vista at home back in October of last year, and with a bit of orientation, Monique has picked up on the OS and its features with no problems. My Dad, whom I introduced to the world of technology and its benefits around ten years ago, has worked his way into the more advanced features of the OS after we upgraded his system last winter. They both made the transition with little effort.

The OS does improve a user's computing experience. The user needs to know that those features are there before their experience improves!

I do believe that the so called "negative" side of the OS does not exist. The problem has more to do with third parties not having their stuff together for drivers, or application coding trying to run over Vista's new security enhancements. This in turn damages a user's perspective of the OS and its abilities.

All in all, I agree: "The Wow is Now".

And, to the old guard ... remember managing those TSRs?!? ;)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Business Principles: SBS, The Job Interview, and a Raised Eyebrow or Two

Whenever we have guests for the first time at home, there is always the obligatory tour around the house.

Nothing gets more raised eyebrows than the following:

SBS and Web on the feezer

On the left is our W2K3 Web Edition box that publishes HTML and PHP/MySQL sites, as well as DNS to the Web. On the right is our SBS 2K3 R2 Premium box serving our home network with ISA providing filtering for the Web facing services.

It isn't hard to see what is going through the observer's minds by the expressions on their faces: Everything from knowing grins, mischevious grins, or deer in the headlights. They all get a bit of an explanation depending on their technical abilities.

And, it brings up something that we think is very relevant in any person we may consider to help us out either under contract or via being employed in our company: Motivation and Experience.

We are very limited on the way an interview can proceed on the first visit in Canada. But, we can ask experience related questions:

• How many computers/servers do you have at home?
• How many virtual machines do you run and what are they?
• VMWare or MS VS and why?
• Dual Boot and what OSs?
• How many years in the industry?
• What is your operating system of choice and why?
• What is the approximate mean throughput of a Gigabit connection (trick question too: duplexed or not!)?
• Name 5 wizards in SBS.
• What are the benefits of ISA on SBS?
• LAMP?
• *BSD?
• Tiger?
• Looking forward to Leopard?
• Fusion or Parallels?

With these questions and more, we can better understand the candidate's motivation for being there. We tend to lean towards those who are passionate and motivated by that passion to delve deeper into the areas they love. There seems to be a direct correlation between the number of machines at home and the person's passion for what they are doing! ;)

And why not? It is the reason we are doing what we are doing! If it wasn't, then when things begin to seemingly fall apart, nothing seems to work, clients are upset because something isn't working as it should, a vendor just bailed on us, there seems to be nothing in the future for us, etc, etc, then that would be the distinguishing point between those who are motivated to get beyond "The Dip" and those who would walk away.

Karl Palachuk has a good blog post on the subject of "The Dip": Mike Writes about Right-Sizing.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Changing Exchange MailBox Storage Limits

If a user forwards an email that comes to them indicating that they are near their mailbox storage limit, then we need to increase that storage amount, or set their AutoArchive to pull data out more aggressively.

A quick method for changing the 200MB limit on a person's mailbox store size:

In the Server Console:

1. Advanced Management
2. Right click on Exchange Organization and properties
3. Tick both Display routing groups and Display administrative groups
4. Close the Console after clicking Apply and OK.
5. After reopening, go to Advanced Management
6. MYDOMAIN (Exchange)
7. Administrative Groups
8. first administrative group
9. Servers
10. MySBSServer
11. First Storage Group
12. Right click on Mailbox Store and Properties
13. Click the LIMITS tab.
14. Change the Issue Warning and Prohibit send and receive amounts to something higher that is appropriate to your organization.
15. APPLY and OK.
16. Close console or move onto the next admin task.

The 200MB limit is definitely something we change right out of the box. We have clients that have 1GB to 2GB mailbox sizes. In their cases, now that we are moving our clients over to a ShadowProtect workstation environment, we can get more aggressive with our AutoArchive Group Policy settings and not worry about SOX/HIPAA or the like compliance.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - RWW, Windows Vista & Connecting Remote Drives

In some cases, we have clients who need their local machine to be physically connected to the remote desktop by linking the hard drives via their Remote Desktop session.

To do that in Windows Vista, the Remote Web Workplace (RWW) certificate needs to be imported to the "Trusted Root Certification Authorities".

But first, one must Trust the RWW site. After navigating to the RWW site:

1. Double click on the planet at the bottom right of IE.
2. Click Trusted Sites.
3. Click the Sites button.
4. Add the RWW URL which will be sitting there.
5. Close the Internet Security window.
6. Close the browser.

After opening the browser:

1. Go back to the RWW site.
2. Click on the red shield in the Address Bar after clicking past the initial certificate warning.
3. Click view certificate.
4. Click the Import button.
5. During the Import process, choose the "Place all certificates in the following store" radio button.
6. Click the browse button.
7. Choose "Trusted Root Certification Authorities".
8. Click OK, Next, Yes, and so on until finished.
9. Close the browser, reopen it and navigate to the RWW site.

One should no longer receive the certificate warning, and be able to select the connect local drives option when connecting to a remote desktop.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

System Builder Tip: Intel RAID Controllers At-A-Glance

We primarily install Intel RAID controllers in our server builds.

One of the main reasons we now stick with Intel controllers is due to hot swap enclosure compatibility questions. When we are going to install a SRCSAS18E and 10 hot swap drives with an Intel Hot Swap Enclosure or Enclosures, we would configure the following in a SC5400 chassis:

• SRCSAS18E (120 Drive capable)
• 4 Drive Hot Swap Enclosure with Expander (2 SATA Connectors)
• 6 Drive Hot Swap Enclosure (6 SATA Connectors)

Here is a link to Intel's RAID products:

• Intel RAID Controller list including integrated, PCI-E, PCI-X, and PCI: Intel RAID Controllers.

A secondary reason for us sticking with Intel RAID controllers is their support for the channel. As an Intel Associate Member, we have a single point of contact for all of our support questions including immediate RMA service for a component.

Our membership has been very beneficial to us! If you are a system builder, and registered with the big 3 distributors, then check out the program.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows Vista - Creative X-Fi Snap, Crackle, & Pop Noises on Vista x64 with 4GB+

No, we are not talking about the breakfast cereal! ;)

It seems that there is an issue with the Creative X-Fi sound cards and their drivers on Windows Vista x64 with 4GB of RAM or more.

After installing the drivers, the sound coming up right the first time, it was a complete and utter shock to have this incredibly rude sound screaming from the speakers. Good thing no one was holding their tea or coffee at that point! :O

So, after a great deal of searching, we came up with this: Vista X64, released drivers, scratchy / snap / crackle sound - XFI. The Creative Forum posts are dated in March or thereabouts. Apparently there were a number of people with the sound problem if they had 4GB of RAM or more.

Fast forward to May: Creative Sound Blaster X-Fi series Vista Driver 2.15.0002 - 30th May. These are the drivers that are still available via Creative's Windows Vista x64 download page. Guess what? Still the huge snap-crackle-pop and static noises from the card on boot up. This is not the case for everyone however. For some, the noise went away and the card started to produce the proper sounds.

BTW, Creative has pulled out native support for digital sound decoding, such as Dolby and DTS Digital signals, at the driver level. One has to go out and purchase some sort of video player that can do it. Not too sure about the ability to pass digital out of the system for decoding on an audio/video receiver yet.

For now, a workaround is to hit the Device Manager and uninstall the card after a reboot, rescan for new hardware, and allow itself to install again. For the most part, it works almost every time. When it doesn't, it is pretty shocking.

It means turning those speakers off before leaving, or they could be damaged.

Hopefully, Creative will get their stuff together and work out what the problem is, and update their drivers accordingly.

UPDATE 2007-11-12: There is a new driver set for the X-Fi on Windows Vista x64. They are dated November 5, 2007.

This is the Canadian Link: Sound Blaster X-Fi Elite Pro on Windows Vista x64.

The drivers make a huge improvement on the sound card's performance. MSN pings actually work now, the click sounds in IE are working for the most part, and the sound is way better.

Good on Creative!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

Windows Vista - Fresh Install BitLocker Drive Prep

This process was pointed out by Chris Knight in our previous post: Windows Vista - BitLocker caveat - Or maybe not?.

From the TechNet article - Windows BitLocker Drive Encryption Step-by-Step Guide:

Partition a disk with no operating system for BitLocker

In this procedure you start the computer from the product DVD and then enter a series of commands to do the following:

• Create a new 1.5 GB primary partition.
• Set this partition as active.
• Create a second primary partition using the rest of the space on the disk.
• Format both new partitions so they can be used as Windows volumes.
• Install Windows Vista on the larger volume (drive C).

Note:
You must create a second active partition for BitLocker to work properly.

Your drive letters might not correspond to those in this example. In this example, the operating system volume is labeled C, and the system volume is labeled S (for system volume). In this example, we also assume that the system has only one physical hard disk drive.

To partition a disk with no operating system for BitLocker

1. Start the computer from the Windows Vista product DVD.
2. In the initial Install Windows screen, choose your Installation language, Time and currency format, and Keyboard layout, and then click Next.
3. In the next Install Windows screen, click Repair your computer, located in the lower left of the screen.
4. In the System Recovery Options dialog box, make sure no operating system is selected. To do this, click in the empty area of the Operating System list, below any listed entries. Then click Next.
5. In the next System Recovery Options dialog box, click Command Prompt.
6. Use Diskpart to create the partition for the operating system volume. At the command prompt, type diskpart, and then press ENTER.
7. Type select disk 0.
8. Type clean to erase the existing partition table.
9. Type create partition primary size=1500 to set the partition you are creating as a primary partition.
10. Type assign letter=S to give this partition the S designator.
11. Type active to set the new partition as the active partition.
12. Type create partition primary to create another primary partition. You will install Windows on this larger partition.
13. Type assign letter=C to give this partition the C designator.
14. Type list volume to see a display of all the volumes on this disk. You will see a listing of each volume, volume numbers, letters, labels, file systems, types, sizes, status, and information. Check that you have two volumes and that you know the label used for each volume.
15. Type exit to leave the diskpart application.
16. Type format c: /y /q /fs:NTFS to properly format the C volume.
17. Type format s: /y /q /fs:NTFS to properly format the S volume.
18. Type exit to leave the command prompt.
19. In the System Recovery Options window, use the close window icon in the upper right (or press ALT+F4) to close the window to return to the main installation screen. (Do not click Shut Down or Restart.)
20. Click Install now and proceed with the Windows Vista installation process. Install Windows Vista on the larger volume, C: (the operating system volume).

In our case, we always setup a small partition at the end of the disk for the Swap File. So, we will format as follows:

• BitLocker Partition T: (Active)
• System Partition C:
• Swap File Partition: S:

We are in the process of setting up one of our high performance workstations in the office with a fresh install of Windows Vista Ultimate x64 with the intent of setting up BitLocker and running a few drive scans after the fact.

We will be using this x64 based station as a litmus test for the extra memory capabilities of Vista x64 and Adobe Create Suite CS3 performance among other things.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Backup and SS4000-E Intel NAS

Besides using ShadowProtect on our servers, we have a couple of SS4000-E Intel NAS devices to keep live data mirroring on.

Part of our maintenance routine is to use a compressed air source we have in our shop (150psi compressor with dried air) to blow out any equipment we work on.

We had this unit apart to clean out all of the fuzzies and dust. Our office/shop is on the fringes of the city, so there are a lot of fields and bush areas close by. Plus, the construction around us is huge as the area is starting to be developed.

So, we shut down this box and cleaned it out.

When we booted it back up, one of the drives was down. This particular unit has 4 x 300GB Seagates in RAID 5.

We swapped out the "dead" drive and ran the scan on the SS4000. It did not pickup the new drive. A reboot later, and still no sign of the new drive.

We pulled it apart, made sure to give it a good looking over to make sure none of the contacts were dirty and put it back together with the original drive (it tested out okay).

On this boot up, we received a degraded array message, along with a "rebuilding" status for the array. This time around, it had picked up the original drive, but not the data on it.

So, we will keep an eye on this unit to see if it fails the same drive again. If it does, we will swap the unit out for another one with Intel.

The unit is about a year old and has been stable up to this point. We do have a lot of them out there doing similar duty with no issues to date.

There is a firmware update that was released earlier this year that allows for drives larger than 500GB: Intel SS4000-E Downloads Page. Keep in mind that this firmware update will destroy any data on the device.

And, one more point: To rebuild a degraded 900GB RAID 5 array (4x 300GB) on this unit is approximately 17 hours with no other activity to or from the device. Start moving data on or off of the S4000-E and that time quadruples.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS - Post Install - Rename that Administrator Account

There are a number of arguments we have heard over the years about "Security by Obscurity" not working.

In some cases, such as in the case of moving ports about, this may be true. A port sniffer can run the full 65K+ ports in very short order.

In the case of renaming the administrator account, this is not the case. At least, we haven't heard a convincing argument for not renaming the account yet. In our experience, there are many circumstances in life where one can discover that "Security by Obscurity" does indeed work.

So, we change the name of the admin account on all of our SBS installations. But, we do things in two tiers, that is the Group Policy Object (GPO) for the change is at the domain level, but we set another GPO at the workstation level that is enforced to change it again.

Here is a screen shot of a GPO we create by default on all of our SBS installs:

Default Domain Security Policy

As you can see, there are a number of settings that we enable by default to tighten things down. This particular screen shot is of one of our TechNet Plus SBS lab setups.

In this case, we set the default domain admin account to be renamed to: technetadm1n

In our case, we tailor the admin account to our client's circumstances. Of course, we never use their company name, or portion of their company name, for the changed admin account.

One of the objections heard to renaming the account, is that it is public. To mitigate this aspect, we create a workstation level GPO:

SBSComputers Security Policy

After creating the GPO, we right click on it, as in the screenshot, and click on "Enforced". Thus, any settings in the SBSComputers Security Policy that are different than the domain level settings will take precedence.

In this case, we make the following change in the SBSComputers Security Policy:

Rename administrator account: "Administrator"

In this example, we change it back to the default, which causes the Local Admin Account to be set back to being named Administrator. That would be the name to use to log on to the local machine with local admin rights.

One could also set an alternative name for the local administrator depending on the client situation.

With the ability to assign user management privileges to an on-site person via the "Power User" account level, there is no reason why the only people to know the admin account access are the company's partners or contact partner, and us, the supporting I.T. organization.

And, to conclude, the argument we use: If one can't first find the door, how can one pick the lock?

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.