You contacted your web guy/gal, instructed him/her as to what domain name you wanted for your company’s website and once the site was up and running you assumed all was well. But your web guy/gal had a hard time staying on top of things. Response was sometimes, well , non existent. Changes and updates seemed to take forever. That is if they ever got done at all. Of course they were always expedient in sending you the bill! Enough is enough, this is business, so you contact your “new” web guy/gal, explain the situation and arrange for moving forward. No problem says the new hire, just supply me with the user name and password for your hosting account and they’ll get started straight away. What? You don’t have the user name or password. No problem, just contact the hosting account provider and they’ll take care of it. No problem says the hosting provider, just provide them with some simple security verification info and they can take care of it. Hmmmmmm….seems you’re not listed on the account, anywhere! Read the rest of this entry »
Posts Tagged ‘Running’
Lay the proper foundation for your new SBS 2003 server or review your existing SBS 2003 server by using the
Microsoft Windows Small Business Server 2003 Best Practices Analyzer.
The Microsoft Windows Small Business Server 2003 Best Practices Analyzer examines a server that is running Windows Small Business Server 2003 (Windows SBS) and presents a list of information and errors that administrators should review. After collecting information about server configuration, the Windows SBS Best Practices Analyzer verifies that the information is correct and then presents administrators with a list of issues sorted by severity. The list describes each issue and provides a recommendation or possible solution.
Use the Microsoft Exchange Best Practices Analyzer to scan your Exchange server and make sure it complies with Microsoft best practices. Start with the proper foundation and build a solid Exchange network.
Use the Microsoft Exchange Troubleshooting Assistant to help determine the cause of performance, mail flow and database mounting issues on computers running Microsoft Exchange Server. The tool automates specialized troubleshooting steps for identified symptoms.
Anyone who’s ever rebooted a box running Exchange knows how agonizingly slow the wait can be. The slow shutdown is especially pronounced when Exchange is installed on a domain controller – i.e. SBS. Use this simple batch file to speed up the process by stopping Exchange services before Windows shutdown.
Exchange 2003:
net stop MSExchangeES /y
net stop MSExchangeIS /y
net stop MSExchangeMTA /y
net stop MSExchangeSA /y
net stop WinHttpAutoProxySvc /y
Exchange 2007:
net stop msexchangeadtopology /y
net stop msftesql-exchange /y
net stop msexchangeis /y
net stop msexchangesa /y
net stop iisadmin /y
On a typical SBS 2003 box, I prefer to automate this further by calling the batch file via the shutdown group policy:
Default Domain Controller Policy>Computer Configuration>Windows Settings>Scripts (Startup/Shutdown)>Shutdown.
