Tried this with Windows 8.1 and it is easier than you would think as it a command you should be very familiar with.
IPCONFIG /FLUSHDNS
Time server MCSE with a BSc degree in engineering. Returning to work after a career break and studying like mad to update my certifications.
Tried this with Windows 8.1 and it is easier than you would think as it a command you should be very familiar with.
IPCONFIG /FLUSHDNS
If you follow minimum requirements you would allocate 8GB ram for a virtual machine just to evaluate Small Business Server 2011.
Although the motherboard on my Hyper-V system should take this in it stride the jump from its current 8GB to its 16GB max is expensive.
So do I need 8GB to evaluate SBS 2011? I couldn’t if I wanted to as Hyper-V needs some RAM so I gave it 6GB and it fired up. What about 4GB SBS 2008 worked on this and the only reason 2011 wants 8GB is Exchange 2010.
Here is a shot of my task manager running with 4GB of memory and the Exchange Console running. Onwards with the evaluation.
I have also stopped WSUS from downloading but not disabled it.
I have various versions of Small Business Server running in an evaluation environment and don’t want WSUS constantly downloading updates here is a useful guide from the SBS Diva Blog. Should work for SBS 2008 and 2011.
The guide demonstrates how to prevent WSUS downloading updates without mangling the system. You in effect just put WSUS into a monitoring state.
Something always comes up when you are trying to evaluate a product and X weeks/months later you fire up the virtual machine and the Grace Period has expired.
slmgr.vbs –dli will tell you how long the grace period is.
slmgr.vbs –rearm will reset it.
I have tried this on a couple of product the latest being an evaluation version of Small Business Server 2011 and the grace period was reset to 30 days.
If memory serves me then it should work for Windows 2008 evaluations.
Don’t know if it works with products like Windows 8 or Server 2012.
Working in a development environment I tend to reboot my servers more frequently than normal. Shutting down services manually or with a script substantially speeds server shutdown.
Paste the following into a command file:
net stop msexchangeadtopology /y
net stop msftesql-exchange /y
net stop msexchangeis /y
net stop msexchangesa /y
net stop iisadmin /y
I find this greatly speeds the shutdown of a Small Business Server 2008 environment.
Cautionary note:
Watch when deleting drafts in blogger you may accidentally delete a useful post like this.
Warning:
Some of the links mentioned in these webcasts no longer exist as Microsoft is in Server 2012 mode.
Those of you who have been through previous Microsoft product releases will be aware that they go into sales mode and that previous version don’t seem to exist anymore.
I will try to include any useful remaining links such as contributors blogs.
24 Hours of Windows Server 2008
TechNet Webcast: 24 Hours of Windows Server 2008 (parts 01 to 24)
(level 200)
Blogs of contributors to this series
Prepare Yourself for Windows 2008
TechNet Webcast: Prepare Yourself for Windows Server 2008 (Parts 01 to 08)
Windows Server 2008 and SBS 2008 can be configured using a Group Policy (GPO) to clear the last user name from the log on screen.
In an environment where there is a lot of computer sharing, “hot desking” or you are just security conscious you may want to clear the previous user name from the log on screen.
Open the Group Policy Manager and right click on the Default Domain Policy and select edit.
In the left pane you will have drill deep to find the setting.
Interactive logon: Do not display last user name.
Enabling this policy will clear the user name of the previous users from the Windows logon screen.
Further Information:
Windows Server 2008 and SBS 2008 can be configured using a Group Policy (GPO) to display a message when Ctrl+Alt+Del pressed to logon.
This can be used to display a terms & conditions summary or an important systems message prior to a logon attempt.
Open the Group Policy Manager and right click on the Default Domain Policy and select edit.
In the left pane you will have drill deep to find the settings.
Interactive logon: Message title for users attempting to log on.
Interactive logon: Message text for users attempting to log on.
Update these two policy setting to provide a message title and text.
Further Information:
Default SharePoint Services (WSS) 3.0 Database Location
Windows Small Business Server 2008 stores the SharePoint Services 3.0 databases by default in:
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\
The database for CompanyWeb is: ShareWebDb.mdf
Databases that the Windows SharePoint Services engine uses.
SharePoint_AdminContent_{GUID}, SharePoint_Config_{GUID}, WSS_Content, and WSS_Search_Win****.
Additional Databases in folder.
System Databases and SUSDB.
Locate the database files:
If you are supporting a system and want to determine the actual location of the WSS database files.
Connect to Microsoft SQL Server:
Logon to server with account that has access to database.
On most Small Business Server systems this will be the default domain admin account. I tend to use a separate account for SQL administration.
Start, All Programs, Microsoft SQL Server 2005,
right-click Microsoft SQL Management Studio Express
click Run as Administrator.
On the User Account Control page, click Continue.
In the Connect to Server dialog box, do the following:
click Connect
click New Query and copy the following into the query.
select a.name, b.name as 'Logical filename', b.filename from sys.sysdatabases a
inner join sys.sysaltfiles b
on a.dbid = b.dbid where fileid = 1
click Execute.
Location of the database files are displayed, lookup ShareWebDb in the table.
Further Information:
I based this blog entry around the following TechNet article. however, the query for locating the database did not work and I found the alternative included in this entry.
Microsoft TechNet: Repair Windows SharePoint Services after moving the databases
The next-generation release of ISA Server 2006, Forefront Threat Management Gateway 2010, is available for evaluation.
TMG 2010 will not install on Small Business Server 2008. If TMG is important in a SME environment then consider Windows Essential Business Server 2008.
EBS 2008 comes with Microsoft Forefront Threat Management Gateway Medium Business Edition.
Further Information:
Microsoft Forefront: Threat Management Gateway 2010
Microsoft Download: Download Evaluation of TMG 2010
Microsoft EBS 2008: Essential Business Server 2008
Microsoft Comment on ISA and Windows Small Business Server 2008, for customers migrating from SBS 2003 R2 Premium to SBS 2008 and may want ISA or equivalent product.
ISA will not be included in SBS 2008.
Customers with active Software Assurance for SBS 2003:
Customers with active Software Assurance for SBS 2003 R2 Premium will be “made whole” by also receiving a free copy of ISA 2006 Standard Edition along with a separate copy of Windows Server 2003 R2 (since ISA Server 2006 does not run on Windows Server 2008).
Upon the release of the ISA Server successor product, Threat Management Gateway (TMG) 2010, customers will be eligible for a free upgrade from ISA 2006 to TMG 2010 Standard Edition. Once upgraded to TMG 2010, customers will have to maintain software assurance coverage for TMG 2010 independent of their software assurance coverage for SBS 2008 Premium in order to get future upgrades for TMG 2010.
Customers without active Software Assurance for SBS 2003:
Customers without active Software Assurance have to purchase a new SBS 2008 Premium Edition license, corresponding SBS 2008 CALs for each user or device accessing the server software, and a separate ISA 2006 license. And since ISA 2006 does not run on Windows Server 2008, a separate copy of Windows Server 2003 (R2) will be needed as well.
Threat Management Gateway (TMG) 2010
This cannot be run on Windows Small Business Server 2008 or Windows 2003 a second server running Windows Server 2008 will be required.
Essential Business Server 2008 includes a version of TMG but the 3 server requirement is not a realistic option a company of 5 users.
A hardware firewall may be the only consideration for small businesses wishing to deploy SBS 2008.
Further Information:
Microsoft Forefront: Threat Management Gateway 2010
Microsoft Download: Download Evaluation of TMG 2010
Microsoft EBS 2008: Essential Business Server 2008
Operations guide for Microsoft Windows Server Update Services (Level 200)
Architecting and Deploying Windows Server Update Services (Level 300)
Tips and tricks for troubleshooting Windows Server Update Services
Introduction to Security Patching Using Windows Update Services (Level 200)
A Hands-On Guide to Hands-Off Updates with WSUS -- Jeremy Moskowitz [MVP]
Managing the WSUS Automatic Updates Client Download, Install, and Reboot Behavior with Group Pol
Group Policy Client-Side Extension
The updated Group Policy Client-Side Extension enable down-level computers (XP, Vista & Windows 2003) to process new items in Windows Server 2008 (GPO). Group Policy preferences are made up of more than 20 new Group Policy client-side extensions (CSEs) that expand the range of configurable settings in a Group Policy object (GPO). These new preference extensions are included in the Group Policy Management Editor window of the Group Policy Management Console (GPMC).
Examples of the new Group Policy preference extensions:
This update is available via automatic updates, WSUS or can be downloaded from Microsoft.
Further Information:
The following link includes downloads for XP, Vista & Windows 2003.
Microsoft Support: Information about new Group Policy preferences in Windows Server 2008
If you are using remote desktop to manage your servers you will find you cannot take control of the console in Terminal Services Manager.
Can’t remote control Session (ID 0) because Remote Control is disabled on that Session
(Error 0 – The operation completed successfully)
Very annoying as some software can only be installed at the console.
Solution: Run one of the following command.
Command for XP SP2 and Vista no SP
mstsc /v:servername /console
Command for XP SP3, Vista SP1
mstsc /v:servername /admin
Further Information:
This effect systems with updated Remote Desktop Protocol RDP
Changes to Remote Administration in Windows Server 2008
Remote Desktop Services (Terminal Services) Team Blog
The Remote Desktop Connection 7.0 client update enables you to use the new Remote Desktop Services features. These features are introduced in Windows 7 and in Windows Server 2008 R2 and are available for computers that are running Windows Vista Service Pack 1 or Windows Vista Service Pack 2.
Important: verified backup required before proceeding.
You can probably guess by the red lettering that the installation of Service Pack 2 for Exchange 2007 is going to be problematic.
Checking Exchange Version
Running either of the two following command in the Exchange Management Shell (EMS) will produce the ominous AdminDisplayVersion : Version 8.1 (***)
If WSUS had installed SP2 AdminDisplayVersion : Version 8.2 (***)
Install SP2 or Not
The Official SBS Blog explains the problem and mentions a tool they are working on to deploy the service pack. I would agree with the official SBS blog team that for most people waiting for the SP installation tool is the best option.
Gotcha: All future Exchange 2007 Rollup Updates will require SP2 installed and is required for transition to Exchange 2010.
The Microsoft Support solution requires a registry change and stopping and starting of services to cure a list of possible side effects.
After removing a number of machines from an SBS 2008 domain I noticed the Windows Server Update Service (WSUS) still had some Updates in Progress for them.
There was 5 or 6 updates for 3 workstations and 1 member server, even after deleting the machine domain accounts WSUS still wanted to install updates. There does not appear to be anyway to fix this from the SBS Console.
There probably is a proper way to tell WSUS that these machines are no longer domain members but here’s how I resolved it.
Gotcha #1: Do not play with Windows Server Update Services you will break it.
SBS 2008 configures WSUS if you change the configuration outside Windows SBS Console WSUS will stop working.
Gotcha #2: Service packing WSUS do not be tempted by the final dialog box.
When service packing WSUS you will be presented with a dialog box with settings on completion. This is a generic SP for WSUS and does not know it is going on SBS 2008 so gives you the wanna change my configuration dialog … Remember Gotcha #1
“Yes I got caught by both … MCSE … if there’s a button we’ll press it … if there’s a setting we’ll change it!”