Microsoft

Microsoft IPAM (IP Address Management) is a feature that was released in Windows Server 2012 to help administrators manage decentralized DHCP and DNS Servers. Previously administrators may have needed to use spreadsheets to keep track of DHCP Scopes, IP Addresses DNS Names etc but with IPAM installed, a single server can refresh all of this data and put it in a single, always up to date place. Deployment Guidelines There are a few things you should know before installing IPAM. ...

Mobility is no longer a challenge to traditional IT environments, it’s the standard. Users work from home to save office space, need to be connected during sales trips and are consistently not in the corporate office connected to the local area network (LAN). Combine this demand for a mobile workforce with the ever increasing security requirements put forth such as HIPPA and PCI-DSS etc make this a significant hurdle for IT departments. Microsoft Direct Access may be a solution that eases this hardship. ...

These days, companies are dealing more with mobility, than ever before. IT infrastructure is now spread out in the cloud, and users may be working from the road, remote offices or from home. This is making it more difficult to manage a secure IT Infrastructure. Microsoft is taking steps to allow IT Administrators to start controlling machines even when they aren’t connected to a corporate infrastructure. Microsoft Offline Domain Join was released as a new feature with Windows Server 2008 R2. This feature allows a machine that is not directly connected to a network with Active Directory, to be joined anyway. ...

Microsoft has a new file system designed to increase data integrity, scalability and availability called the Resilient File System (ReFS). This file system has leveraged many of the NTFS file system goodies and expanded them to make it more scalable and prevent corruptions. ReFS was released with Server 2012 and at the moment is designed for use with file shares. It cannot be used as a boot volume at the present time, but this file system seems poised to replace NTFS down the road. ...

Microsoft Storage Spaces feature used to handle data redundancy, scalability and performance. Storage Spaces takes a set of Just a Bunch of Disks (JBOD) and pairs them together to allow for; either failures of a disk, gaining the performance of multiple spindles, or gaining the space of multiple disks. Traditionally this has all been handled by creating a Redundant Array of Independent Disks (RAID) group. Some examples of RAID would be: Striping (RAID 0) Mirroring (RAID 1) Parity (RAID 5 or 6) Storage Spaces create a similar type of RAID Group but then throw a virtual disk on top of them so that multiple types of stripes can be used on the same disks. For example, three physical disks can be put into a storage space. From there, three separate types of VDISKs can be created, Mirrored, Spanned and Parity can then be placed on the same set of disks with no issue. The diagram below shows an example. ...

Active Directory (AD) is the base of most enterprise level infrastructures and has been for some time. We have become accustomed to seeing this structure and depending on it. But AD has been a thorn in our side since virtualization has become popular due to the inability to take snapshots. This is no longer the case if your shop is running Windows Server 2012 with Active Directory. With the release of Active Directory 2012, Microsoft has added a new object called the VM GenerationID that allows us to snapshot AD Servers. ...

If you’ve got a some hardware lying around for your lab, Windows Server 2012 may be a great solution for a home storage device. You can now do both block (iSCSI) and NAS (NFS) on the same server, as well as having an OS to install some management apps on it. In my lab, I use this management server to run Veeam for my backups, PRTG network monitor for bandwidth tracking, as well as using this server for both iSCSI targets and NFS mounts. ...

One of the new features in the latest version of Windows Server is the ability to create server groups. When you open the server manager you’ll see some server group options on the dashboard. You can add other servers to manage, or create a new group. Also, pay attention to the “Roles and Server Groups” section at the bottom of the screen which shows some of the server groups that were already set up. ...

 Microsoft has made the Exchange 2013 transition from Exchange 2010 a bit easier than it was in the past. This article should help to explain the process. Prerequisites Before you begin with this endeavor: Make sure that your Exchange 2010 infrastructure has been patched to Exchange Service Pack 3, this includes Edge transport servers, Client Access Servers, Hub Transport Servers and Mailbox Servers. This service pack is required for the coexistence period with Exchange 2013 as noted in the Exchange Team’s Blog. Say goodbye to Exchange 2003. You can not have Exchange 2003 in your organization any longer. Check your DNS Server and Event logs for errors. It’s unlikely that you had DNS errors before an upgrade that you didn’t already know about but it’s certainly worth taking a look just to check. A few minutes of discovery is well worth not having hours of troubleshooting afterwards. Plan your Exchange 2013 infrastructure. This article only explains the transition steps, but you should research and understand what your infrastructure should look like before you start a migration. Do you have multiple sites that need High Availability? Do you need multiple Exchange servers in a Database Availability Group? Do you need to separate your Client Access Server from your Mailbox Server for performance or management reasons, or can you put them on the same box? How many different Mailbox databases should you have? These are important design considerations. Licensing There are two flavors of Exchange 2013. Standard allows for up to five mailbox databases, and Enterprise allows for up to 50. ...

Microsoft Exchange 2010 to Exchange 2013 Transition part 1 Microsoft Exchange 2010 to Exchange 2013 Transition part 3 Microsoft Exchange 2010 to Exchange 2013 Transition part 4 I assume you’ve reached this page because you finished ready part 1 and are now ready to dive into your newly installed Exchange 2013 server. ...