Test Layout

I freely admit that I don't do much with mailbox permissions and I've been stuck in thinking about them much like I did in Exchange 2003. That is, that you can give people the following permission to a mailbox: Send As Send on Behalf Of Full Mailbox (Receive As) Those permissions have been around for a long time and you can use them in combination to provide someone with access to a mailbox and the ability to send as that mailbox. This is useful for shared mailbox or sometime when an assistant needs to do things on behalf of someone. It can also be useful for vacation coverage. In class this week I was asked about applying read only permissions to a mailbox and thought it could not be done. Turns out I was wrong. In Exchange 2010 and Exchange 2007, you can use the Add-MailboxPermission cmdlet to assign read only access to an entire mailbox. If you want to assign permission to just a subfolder within the mailbox you can use the Add-MailboxFolderPermission cmdlet. The Add-Mailbox

In the last little bit I've been playing with imaging systems as part of a project trying to virtualize an old NetWare servers. As part of this I learned of Clonezilla. Clonezilla is open source disk imaging software that can be downloaded as a live CD. Clonezilla has a lot of options: Clone partitions Clone whole disk Clone to file (local disk, Windows share, SSH server, NFS) Clone directly to disk Clonezilla works with multiple partition types. From a Windows perspective, it understands both FAT and NTFS partitions. For any partition type that Clonezilla understands, the blank space in the partition is skipped. For any partition type that Clonezilla does not understand a sector by sector copy is performed. Lately when I've been moving Windows computers with failing hard drives, I've been using ImageX. My general process has been: Boot from WindowsPE disk with ImageX Use ImageX to copy local partition contents to file over the network Replace hard drive Boot from Windows P

A client recently implemented Exchange 2010 as a replacement for an existing externally hosted POP3 mail system. The client is relatively small. So, the plan was to have no coexistence and the real domain name was not used for testing. A new domain name was used for testing. Consequently during testing, all of the external URLs were configured as testdomain.com. During switchover day, we obtained a new certificate with the proper names, including realdomain.com. During testing of OWA, the web browser was redirected to testdomain.com. Aha, I forgot to update the external URL. Exchange 2010 has a nice wizard for updating external URLs for all web services. All fixed up and tested in 10 minutes. A week later, I get a call from the client indicating that there is a certificate problem and users are being redirected to testdomain.com. After some back and forth communication this is only for Outlook Anywhere clients. Outlook Anywhere does not have an external URL, but it does have a host nam