Having work for large organisations with many branch offices it was not an infrequent event to have equipment stolen.
From experience … the people that stole your kit know you will be sending out new kit so they will return for that.
Read Only Domain Controllers (RODC) are designed for insecure environments .. so what do you do if one gets nicked … you follow the procedure on the link below to disable the stolen RODC and reset the passwords on any cached user accounts.
Microsoft Active Directory Lightweight Directory Services (AD LDS) is an independent mode of Active Directory that provides dedicated directory services for applications.
MSDN: Active Directory Lightweight Directory Services
AD LDS can use many of the familiar tools used to manage Active Directory Directory Services (AD DS) even when it comes to using the AD PowerShell Module there is a feeling of “deja vu”.
On the link below you will find a list of Active Directory cmdlets that can be used to manage AD LDS instances.
Windows 2008 R2: Managing AD LDS using the AD PowerShell Module
You can change Outlook 2010 by adding switches to the outlook.exe command.
For example
outlook.exe /resetfolders
Restores missing folders at the default delivery location.
For a full list of switches see the following link.
One of the first things I found with Outlook Web Access 2010 is that you cannot have multiple mailboxes open in separate tabs; you get the following error message.
You can resort to a second browser like Chrome or Firefox to get a second mailbox open. I have tried a second tab in Chrome and get the same result …one mailbox per browser.
The solution
Create a shortcut on your desktop remembering to add <your_servername> without <>.
"C:\Program Files\Internet Explorer\iexplore.exe" -noframemerging /owa">https://<your_servername>/owa
Click the shortcut every time you want an additional OWA session. You can now open multiple OWA mailboxes in separate instances of internet explorer.
By default group policies are applied asynchronously - Fast Logon Optimization . The upshot is that if you update a policy users may logon before the latest policy is applied and it may take a couple of logons before current settings are applied.
I am messing about with GPOs in a test environment so I don’t want to have to constantly rebooting PC or perform multiple logons attempts.
Disable Fast Logon Optimization by using the following
Create or update and existing group policy attached to the OU housing the computers and edit the following.
Computer Configuration
Policies
Administrative Templates
System
Logon
Enable: Always wait for the network at computer startup and logon
