A great new blog has been published over at the Official SBS Blog, that covers a lot of the reasons that SBS installs or migrations fail, and when they do, where to look for log files as to whats gone wrong.
A good bit of reading here.
Aug 04 2010
A great new blog has been published over at the Official SBS Blog, that covers a lot of the reasons that SBS installs or migrations fail, and when they do, where to look for log files as to whats gone wrong.
A good bit of reading here.
Jun 29 2010
If you are trying to load server manager in Server 2008 and you find that the only response you get is error, you may need to run the System Update Readiness Tool (don’t be misled by it’s name!).
This tool will run through your system and find any errors that may cause future updates to fail, which in this case also includes fixing this issue.
The download isn’t small, but will fix your issues. Grab it from here and make sure you grab the right version. Either 2008 or 2008 R2 (32 &64 bit versions both available).
Once you have installed/run the fix, check out the log files here:
Jun 01 2010
Rather than having to type the crazily long URL every time you need to go there, there is a much shorter method, http://et.exbpa.com/
A lot easier to type than http://testexchangeconnectivity.com
May 31 2010
If you are after a good guide to starting off with VHD’s, then this one from MS can’t be missed. If you are working with VHD’s in Windows 7, or Server 2008, then this is a great starting point to build your knowledge from.
Grab a copy of the guide here .
May 28 2010
For a really great guide on designing, installing, and configuring Remote Desktop Services on Windows 2008 R2, check out this guide here from MS themselves.
May 20 2010
Have you ever wondered how Windows allocates physical memory or what’s using it? RAMMap is a new utility for analyzing system RAM usage on Windows Vista and Windows 7 that provides insight never before available. RAMMap shows information about each page of memory, summaries of memory usage by type, views of file data stored in memory, and more.
May 17 2010
To set up a source initiated subscription, that requires minimal intervention, and no thought every time a new server is built, follow these easy steps.
Source computers
If you want to configure this as a one off, to test do the following:
On your source computer, using an elevated command prompt, enter the following:
winrm qc -q
Or if you are running in a domain environment, and want to set and forget:
At this stage you can run gpupdate /force on your source servers, or just allow for the natural flow and wait for the next automatic refresh.
Collector Computer
Run the following command from an elevated privilege command prompt to configure Windows Remote Management:
winrm qc -q
Run the following command to configure the Event Collector service:
wecutil qc /q
You now have 2 options about how you create the subscription. You can either do this through the event viewer, or by using a script.
Via the Event viewer:
4. If you are using certificates, select the one for your system, and select OK.
5. Hit “Select events” and chose the event types, and ID’s that you want to monitor, select OK, and if you are happy with your settings, select OK again.
Via a script
Copy the following code into your favourite text editor, and save it as configurationfile.xml
<Subscription xmlns="http://schemas.microsoft.com/2006/03/windows/events/subscription">
<SubscriptionId>SampleSISubscription</SubscriptionId>
<SubscriptionType>SourceInitiated</SubscriptionType>
<Description>Source Initiated Subscription Sample</Description>
<Enabled>true</Enabled>
<Uri>http://schemas.microsoft.com/wbem/wsman/1/windows/EventLog</Uri>
<!-- Use Normal (default), Custom, MinLatency, MinBandwidth -->
<ConfigurationMode>Custom</ConfigurationMode>
<Delivery Mode="Push">
<Batching>
<MaxItems>1</MaxItems>
<MaxLatencyTime>1000</MaxLatencyTime>
</Batching>
<PushSettings>
<Heartbeat Interval="60000"/>
</PushSettings>
</Delivery>
<Expires>2018-01-01T00:00:00.000Z</Expires>
<Query>
<![CDATA[
<QueryList>
<Query Path="Application">
<Select>Event[System/EventID='999']</Select>
</Query>
</QueryList>
]]>
</Query>
<ReadExistingEvents>true</ReadExistingEvents>
<TransportName>http</TransportName>
<ContentFormat>RenderedText</ContentFormat>
<Locale Language="en-US"/>
<LogFile>ForwardedEvents</LogFile>
<AllowedSourceNonDomainComputers></AllowedSourceNonDomainComputers>
<AllowedSourceDomainComputers>O:NSG:NSD:(A;;GA;;;DC)(A;;GA;;;NS)</AllowedSourceDomainComputers>
</Subscription>
From the command line browse to the folder that you saved the above file in, and run:
wecutil cs configurationFile.xml
May 14 2010
If you want a slightly more flexible, and different set of commands for managing AD, grab a copy of the Quest PowerShell Commands here for free.
There are 32 and 64 bit versions available, and a handy Administrators guide to top it off!
May 14 2010
In order to protect your OU’s from being accidently deleted you have to make sure that they have the correct permissions.
Every time you create a new OU make sure that you select the “Protect container from accidental deletion” option checked.
If you already have your OU structure in place, and want to protect all the current OU’s, there is a couple of ways that you can save yourself a lot of time by not having to click through each and every OU.
1. Using Active Directory module for PowerShell (running as Administrator), enter the following command:
Get-ADOrganizationalUnit -filter * -Properties ProtectedFromAccidentalDeletion | where {$_.ProtectedFromAccidentalDeletion -eq $false} | Set-ADOrganizationalUnit -ProtectedFromAccidentalDeletion $true
To check to see which OU’s are not currently protected us this:
Get-ADOrganizationalUnit -filter * -Properties ProtectedFromAccidentalDeletion | where {$_.ProtectedFromAccidentalDeletion -eq $false} | ft
2. If you have the Quest Powershell Active Direcoty module, you can use the following command to enable protection for all OU’s:
Get-QADObject –SizeLimit 0 -Type OrganizationalUnit | Add-QADPermission -Deny -Account Everyone -ApplyTo ThisObjectOnly -Rights DeleteTree,Delete
If you want to do a one off check, or you are scared of PowerShell, you can right click on an OU (with teh Advanced view turned on) and check the object tab.
Apr 21 2010
For a good run down on how to go about running BES express on SBS 2008, have a read here.
Always make sure you do everything as the besadmin though, otherwise you will run into issues!