Active Directory Replication Status Tool

The Active Directory Replication Status Tool (ADREPLSTATUS) analyzes the replication status for domain controllers in an Active Directory domain or forest. ADREPLSTATUS displays data in a format that is similar to REPADMIN /SHOWREPL * /CSV imported into Excel but with significant enhancements.
Specific capabilities for this tool include:

    • Expose Active Directory replication errors occurring in a domain or forest
    • Prioritize errors that need to be resolved in order to avoid the creation of lingering objects in Active Directory forests
    • Help administrators and support professionals resolve replication errors by linking to Active Directory replication troubleshooting content on Microsoft TechNet
    • Allow replication data to be exported to source or destination domain administrators or support professionals for offline analysis

System Requirements

Supported Operating System

Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Vista, Windows XP

      • ADREPLSTATUS does not install on server core installs of Windows
      • Windows 2000 not supported due to lack of support for .NET Framework 4.0

    Domain membership requirements:

      • Must be joined to the Active Directory domain or forest you intend to monitor

    .NET Framework requirements:

      • .NET Framework 4.0 (you may be prompted to install .NET Framework 3.5.1 first on Windows Server 2008)

    Required User Credentials:

      • Target forest/domain user account

    Supported DC OS versions that can be monitored by ADREPLSTATUS:

      • Windows Server 2003
      • Windows Server 2003 R2
      • Windows Server 2008
      • Windows Server 2008 R2
      • Windows Server 2012

      image

Windows Server 2012: Convert server Core to server with a Gui

  1. Create a folder to mount a Windows Imaging File (WIM) in with the command mkdir c:\mountdir

  2. Determine the index number for a Server with a GUI image (for example, SERVERDATACENTER, not SERVERDATACENTERCORE) using this command at an elevated command prompt: Dism /get-wiminfo /wimfile:<drive>:sources\install.wim

  3. Mount the WIM file using this command at an elevated command prompt: Dism /mount-wim /WimFile:<drive>:\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly

  4. Start Windows PowerShell and run this cmdlet:

    Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

  5. Alternatively, if you want to use Windows Update as the source instead of a WIM file, use this Windows PowerShell cmdlet:

    Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart

Kemp Exchange 2010 Templates

Kemp released Exchange 2010 Templates witch makes configure a Kemp Loadmaster easier

Microsoft® Exchange 2010 Templates

Core services: MAPI, SMTP and Unified HTTP/HTTPS
Extended services: Per-service HTTP/HTTPS
Additional Services: POP, IMAP and SMTP

Ward 06-07-2012: Fixed Links

Windows Server 2012 Release Candidate Build 8400 in VMware Workstation Technology Preview 2012

This procedure describes how to install Windows Server 2012 in VMware Workstation. The following versions are used:

  • VMware Workstation Technology Preview 2012 e.x.p Build-646643
  • Windows Server 2012 Release Candidate Datacenter Build 8400

In VMware Workstation Technology Preview 2012 create a new VM with the following settings:

  • New Virtual Machine
  • Custom (advanced)
  • Workstation Tech Preview
  • Select “I will install the operating system later”
  • Select “Microsoft Windows” and select as version “Windows 8 x64”
  • Set the Name and Location
  • Minimal 1 processor, 1 core
  • 2048 MB memory
  • Select “Use network address translation (NAT)”
  • Select “LSI Logic SAS”
  • Create a new virtual disk
  • SCSI
  • 60 GB disk size
  • Leave default disk file
  • Finish
  • After the VM is created, edit virtual Machine settings and browse for the Windows Server 2012 ISO in the the CD/DVD option

image

Edit the VMX file  and add the following line to the end to of the VMX file:

vmGenCounter.enable = FALSE

During the installation choose for the Windows Server 2012 Release Candidate (Server wit GUI)

Special thanks to my colleague Ivo Beerens

Exchange 2010 SP2 RU1 Change in CAS to CAS Proxy

The Exchange Team did a change in CAS to CAS proxy behavior between servers running Exchange 2010 SP2 RU1 and servers running older versions of Exchange.

The SP2 RU1 package introduced a change to the user context cookie which is used in CAS-to-CAS proxying. An unfortunate side-effect is a temporary incompatibility between SP2 RU1 servers and servers running earlier versions of Exchange. The change is such that earlier versions of Exchange do not understand the newer cookie used by the SP2 RU1 server. As a result, proxying from SP2 RU1 to an earlier version of Exchange will fail with the following error:

Invalid user context cookie found in proxy response

The server might show exceptions in the event log, such as the following:

Event ID: 4999
Log Name: Application
Source: MSExchange Common
Task Category: General
Level: Error
Description: Watson report about to be sent for process id: 744, with parameters: E12, c-RTL-AMD64, 14.02.0283.003, OWA, M.E.Clients.Owa, M.E.C.O.C.ProxyUtilities.UpdateProxyUserContextIdFromResponse, M.E.C.O.Core.OwaAsyncOperationException, 413, 14.02.0283.003.

Not all customers are affected by this. But since we received a few questions about this, we wanted to let you know about the change. Many Exchange customers do not use proxying between Exchange 2010 and Exchange 2007 but rather use redirection, which is not affected by the change. However, if you are using CAS-to-CAS proxying, where an Exchange 2010 SP2 RU1 Client Access server is proxying to an earlier version of Exchange 2010 or Exchange 2007 Client Access server, then you are affected by the change.

If you are affected, it is important to note that this issue is temporary and will exist only until all of the CAS involved in the CAS-to-CAS proxy process are updated to Exchange 2010 SP2 RU1. Thus, if you are affected by this problem, simply deploy SP2 RU1 on the relevant Exchange 2010 servers and the issue no longer exists.

If you use CAS-to-CAS proxy between Exchange 2010 and Exchange 2007, we will have an interim update (IU) for Exchange 2007. Availability of the IU will be announced on this blog.

Server proxy version
Server being proxied to
Action to take

Exchange 2010 SP2 RU1 –> Any version of Exchange 2010 older than SP2 RU1
Apply Exchange 2010 SP2 RU1 to all servers involved in proxy process

Exchange 2010 SP2 –-> RU1 Exchange 2007
Hold off deployment of Exchange 2010 SP2 RU1 until you deploy the Exchange 2007 interim update (IU)

SOURCE: Exchange 2010 sp2 ru1 and cas to cas proxy incompatibility

VMware Workstation 8

What’s New

This release of VMware Workstation adds the following new features and support.

Installation Changes and Enhanced Keyboards

The hardware requirements to install this version of Workstation have changed. Workstation now requires a relatively modern 64-bit CPU. See Installation Requirements for details.

The keyboard filter driver is no longer installed by default. When the driver is not installed, the enhanced keyboard functionality is unavailable and you must press Ctrl-Alt-Ins instead of Ctrl-Alt-Del to send a Ctrl-Alt-Del keystroke to the guest. To use the enhanced keyboard functionality, you must perform a custom installation and select the component. If you select the component, you must reboot whenever you install or uninstall Workstation.

Virtual Hardware Improvements

This version of Workstation includes many hardware improvements. To try new hardware features, you must upgrade the hardware version of your virtual machine or create a new virtual machine that uses the latest virtual hardware version.

  • The display technology has been changed to provide a better experience for Unity users and users who have multiple monitors. These changes also allow you to add a projector to your laptop without restarting your virtual machine.
  • Virtual machines can now support up to 64GB of memory. The host system should have more than 64GB of memory to use this feature.
  • An HD Audio device is available for Windows Vista, Windows 7, Windows 2008, and Windows 2008 R2 guests. The HD Audio device is compatible with the RealTek ALC888 7.1 Channel High Definition Audio Codec.
  • USB 3.0 support is available for Linux guests running kernel version 2.6.35 or later (Ubuntu 10.10) through a new virtual xHCI USB controller. To enable this feature, add the following line to the .vmx file: usb_xhci.present = “true”. Do not enable this feature for Windows guests. Because Windows does not currently have a generic xHCI driver, this feature will not work in Windows.
  • Bluetooth devices on the host can now be shared with Windows guests. With the latest hardware version, Bluetooth devices that are paired to the host system radio are available to Windows guests and can be paired from within the guest. You should not pair Bluetooth audio devices, such as headphones, or Bluetooth input devices, such as keyboards and mice, to a guest.
  • You can now enable Virtual VT-X/EPT or AMD-V/RVI in the processor settings interface. With this feature, applications running in a guest can take advantage of these virtualization technologies. You can also run 64-bit guest operating systems inside of vSphere running inside Workstation.
New User Interface

The Workstation user interface has been updated to include new menus, toolbars, and an improved preferences screen.

  • The favorites sidebar has been replaced with a virtual machine library. Instead of identifying every virtual machine created in Workstation as a favorite, the library is a comprehensive list of all of the virtual machines that Workstation users create, open, or access.
  • A new folder summary page helps you to better manage a group of related virtual machines. Live thumbnails make it easy to see what is happening in running virtual machines.
  • The full screen toolbar has been updated so that you can do more without having to leave full screen mode. Quick switch mode is no longer needed.
What Happened to Teams?

Although at first it might appear that the teams feature has been removed, you can add team attributes to any virtual machine in this version of Workstation.

  • The team structure has been converted to a simple folder of virtual machines.
  • A new advanced settings dialog box has been added for network adapters to let you throttle the bandwidth of incoming and outgoing transmissions and simulate packet loss.
  • You can perform power operations on several virtual machines at the same time by selecting virtual machines on the folder tab and pressing the power button on the toolbar. If all of the virtual machines in a folder are in the same power state, you can select the folder to perform a power operation on all of the virtual machines in the folder.
  • You use a global Workstation preference to configure the delay between powering on virtual machines.
  • To implement LAN segments, you can use traditional VMnets or put all of the virtual machines that you want to communicate on the same custom VMnet.
Shared Virtual Machines and AutoStart

You can share virtual machines with remote users in this version of Workstation. A shared virtual machine can be accessed remotely by other instances of Workstation. Workstation moves virtual machines to the shared virtual machines folder, where the VMware Host Agent service manages them. The VMware Host Agent service is used by other VMware products, including VMware Server and vSphere, and provides additional capabilities required by professional users. An extensive permissions interface lets you control the users who can access and use shared virtual machines.

You can use the new AutoStart feature to configure shared virtual machines to start with the host system. You can also configure AutoStart for shared virtual machines on remote hosts running Workstation and ESX 4.x and later.

Remote Connections

In this version of Workstation, you are no longer constrained to working only with virtual machines that your computer has enough power to run. You can use the new Connect to Server feature to connect to remote hosts running Workstation, ESX 4.x and later, and VMware vCenter Server. After connecting to a remote host, all of the virtual machines that you have permission to access are displayed in the virtual machine library.

Upload to ESX/ESXi and vCenter Server

VMware OVF Tool is now integrated with Workstation so that you can upload a virtual machine from Workstation to a remote server running ESX, ESXi, or vCenter Server. After connecting to a remote server, you drag the virtual machine from the local My Computer section of the virtual machine library to the remote server. A wizard walks you through the process.

Documentation Changes

This version of Workstation includes several important documentation changes.

(NEW) Getting Started with VMware Workstation
Describes how to install and upgrade Workstation, create a typical virtual machine, and perform common virtual machine operations.

Using VMware Workstation
(previously VMware Workstation User’s Guide)
Describes how to create typical, custom, and shared virtual machines, add virtual devices, configure network connections, connect to remote servers and use remote virtual machines, upload virtual machines to remote servers, and perform all virtual machine operations.

Getting Started with VMware Player
(previously VMware Player Getting Started Guide)
Now contains complete information on installing and using Player.

Online help
Has been redesigned to provide context-sensitive help and information on performing common tasks. For complete information on using Workstation and Player, see the guides.

(NEW) Installing and Configuring VMware Tools
Contains comprehensive information on installing, upgrading, and configuring VMware Tools.

Top of Page

Installation Requirements

When you install Workstation, the installer performs checks to make sure the host system has a processor that meets the following requirements. You cannot install Workstation if the host system does not meet these requirements.

  • 64-bit x86 CPU
  • LAHF/SAHF support in long mode

You can use CPU-Z or a similar utility to determine if the host system CPU is 64-bit capable. CPU-Z shows EM64T (Intel) or AMD64 (AMD) if the processor is 64-bit capable.

If you plan to install a 64-bit guest operating system in a virtual machine, the host system must have one of the following processors. Workstation will not allow you to install a 64-bit guest operating system if the host system does not have one of these processors.

  • AMD CPU that has segment-limit support in long mode.
  • Intel CPU that has VT-x support. VT-x support must be enabled in the host system BIOS. The BIOS settings that must be enabled for VT-x support vary depending on the system vendor. See VMware KB article 1003944 for information on how to determine if VT-x support is enabled.

Top of Page

Known Issues

The known issues are grouped as follows:

Remote Connection and Remote Virtual Machine Issues
  • When Workstation is installed on a Linux host, VMware Workstation Server writes the core file to /usr/bin instead of to /var/core or /var/log/vmware.
  • You cannot use Workstation to create a remote virtual machine on an ESX or ESXi 4.1 host if the virtual machine name contains non-ASCII characters.
  • When you upload a virtual machine to a remote server (VM > Manage > Upload), Workstation modifies the MAC address and PCI slot number of the virtual Ethernet device in the newly created remote virtual machine. Network errors can occur in the remote virtual machine if the network settings in the guest operating system require the original network hardware configuration.
    Workaround: Change the network settings in the guest operating system in the remote virtual machine to match the new network hardware configuration.
  • VMware Workstation Server occasionally crashes on a 32-bit Red Hat Enterprise Linux 6.x host.
Role and Permission Issues
  • On a Windows host, if you edit a permission, assign the Administrator role, and then immediately click Remove to delete the permission, the original permission still exists when you reopen the Permissions dialog box.
Shared Virtual Machine Issues
  • On Windows hosts, if a shared virtual machine has a floppy drive that is configured to connect at power on, and a remote user powers on the virtual machine, a dialog box appears on the host system asking whether to connect the device every time the virtual machine powers on. If you click Yes to close the dialog box on the host system after the virtual machine is completely up and running on the host system, Workstation crashes on the host system.
  • On a 32 or 64-bit Windows 7, 64-bit Windows 2008 R2, or 32-bit Windows XP Professional SP3 host, if you uninstall Workstation, preserve the configuration, and then reinstall Workstation to a different path, the Shared VMs item is unavailable in the virtual machine library.
  • On a Windows host, if you create a virtual machine with a name that contains non-ASCII characters in the New Virtual Machine wizard, you cannot share the virtual machine with the Move the virtual machine option if the destination path is other than the system operating system location. The sharing process stops with the error message Failed to move VM to destination path.
    Workaround: If you want to share the virtual machine, you must use only ASCII characters in the virtual machine name when you create the virtual machine in the New Virtual Machine wizard.
Display and Input Issues
  • On an Ubuntu 11.04 host, the virtual machine icon does not appear on the system tray when you set the Show tray icon setting (Edit > Preferences > Workspace) to Always or When a virtual machine is powered on.
    Workaround: Whitelist vmware-tray as an application that can show system tray icons in Ubuntu 11.04. Alternatively, enable Notification Area (Systray) for all applications, for example:
    gsettings set com.canonical.Unity.Panel systray-whitelist "['all']"
    After you run the command, log out and log back in. The command can take several minutes to take effect.
  • On a Fedora 15 host, powering on a virtual machine that has DirectX 9 accelerated graphics enabled might fail with the error "Unable to change virtual machine power state: Cannot find a valid peer process to connect to."
    Workaround: Deselect the Accelerate 3D graphics setting (VM > Settings > Hardware > Display) to disable DirectX 9 accelerated graphics in the virtual machine.
  • When you enter Unity mode in an Ubuntu 11.04 guest, application menus do not appear for applications that were opened before entering Unity mode. Application menus do appear for applications that are opened from the Unity launch menu after entering Unity mode.
    Workaround: Disable the APPMENU (Global menu) in the Ubuntu 11.04 guest. See the Ubuntu documentation for more information.
  • After you upload a Windows XP virtual machine from the local host to a remote server, you cannot autofit the guest in full screen mode. This problem occurs because VRAM is reduced to 4 MB when the virtual machine is uploaded to the remote server.
Folder and Team Conversion Issues
  • When you select a newly created folder in the Workstation library, the toolbar power option button is dimmed and you cannot perform batch power operations on the virtual machines in the folder.
    Workaround: If you select a virtual machine in the folder, move the selection off the virtual machine (for example, click anywhere on the folder tab), and then select the folder in the library again, the toolbar power option button becomes available.
Device Issues
  • On Windows hosts, Player crashes if you click Connect or Disconnect in the Removable Devices menu before the console appears.
  • An Ubuntu 11.04 host might crash when you try to connect a USB device to a running virtual machine from the status bar icon’s context menu. This problem typically occurs after Workstation is freshly installed, the host is rebooted, and the first time the device is connected to the virtual machine.
Physical Machine Virtualization Issues
  • When simple file sharing or UAC is enabled on the physical machine, the Virtualize a Physical Machine wizard returns an "incorrect user credentials" error instead of an error message that indicates simple file sharing or UAC must be disabled before virtualizing the physical machine. See the online help or Using VMware Workstation for information on preparing a physical machine for virtualization.
  • You cannot use the Virtualize a Physical Machine wizard if the Workstation installation path contains non-ASCII characters.

Free eBook: Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime

Microsoft released Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime (ISBN 9780735656949), by Katherine Murray, as a free eBook.

To download your free PDF eBook, click here or click on the picture. Updates to this eBook, as well as additional eBook formats, will become available in the future, so check this blog for updates.

Introduction

Let’s hear it for freedom. Freedom from your desk. Freedom from those ­boring managers’ meetings. Freedom to work anywhere, with anyone, anytime, on almost any device. Sounds good, right?

Office 365 is Microsoft’s smart and simple answer to cloud computing. Using the various programs in Office 365, you can do all the tasks you’re used to doing in your favorite Office applications—write documents, create presentations, check email, manage your calendar, crunch numbers, and more—and then share what you create in real time on a team site, design and publish a website, and even create and host live online meetings while you’re traveling on the train, sitting in a coffee shop, or dialing in on your phone.

This book shows you how you can use cloud computing—and ­specifically, ­Office 365—to get more done, collaborate more easily, and work more ­flexibly than you ever have before. From the necessary how-tos about ­creating and administering your Office 365 account and working with the various Office 365 programs to sharing files with your team, creating a team site, using Office Web Apps, and holding online meetings, you’ll discover how easy it is to work online and off, accessing and sharing your files whenever you need to. After you learn about each of the core programs, you can try strategies for building successful teams, and get some good ideas on practical ways you can put all this cloud power to work.

Who This Book Is For

Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime is all about cloud solutions for small businesses, focusing on the core software services (Microsoft Exchange Online, Microsoft SharePoint Online, Office Web Apps, and Microsoft Lync), and demonstrating ways you can create, manage, and lead teams effectively using the communications and collaborative online tools.

A Quick Roadmap

Microsoft Office 365: Connect and Collaborate Virtually Anywhere, Anytime is organized in three parts to help you learn about different aspects of setting up and ­working with Office 365.

Part I, “Finding Your Place in the Cloud,” takes a look at the way people are working in the cloud today and introduces you to Office 365. Chapter 1 looks closely at teams, both inside and outside the office environment, and it takes a look at the way Office 365 offers a greener choice for small businesses. Chapter 2 shows you how to create an Office 365 account and set up a profile, and it gives you a big-picture tour of Office 365 so that you can begin planning just what you want to do with the tools. Chapter 3 is for the team manager or person who will be managing the Office 365 site; you’ll learn how to ­customize the site, add mobile devices, and set up and manage Microsoft Exchange, Microsoft SharePoint, and Microsoft Lync online.

Part II, “Teamwork in the Cloud,” is your guide to setting up, organizing, ­managing, and helping your team be successful using Office 365. ­Chapter 4 spotlights all the team features you can use to get everybody on the same page, calendar-wise; you’ll also find out how to share files, hold online ­meetings, instant message each other, and broadcast presentations. Chapter 5 walks you through creating, editing, and sharing a team site. Chapter 6 shows you how to create document libraries, share files with team members, and manage the files in SharePoint Online. You’ll also find out about working with file versions, tracking file changes, and comparing and merging files. Chapter 7 shows you how to create and use workflows to keep your team moving in the right direction, and Chapter 8 introduces all things Web App by shining a light on the capabilities of the various tools and showing you how to work with files online, coauthor documents, edit worksheets, broadcast presentations, and share notebooks. Chapter 9 rounds out this part of Office 365 by focusing on mobile technologies: find out how to use the various Office Mobile applications to review, edit, and share the files you develop with your team.

Part III, “Connecting in Real Time,” shows you how to use the ­communication and instant-messaging options in Office 365 to stay in touch with your team in real time. In Chapter 10, “Email and Organize with Office 365,” you learn how to use Outlook Web App to import and manage contacts, set email preferences, organize mail ­folders, work with your calendars and tasks, and more. Chapter 11, “Talking it Over with Microsoft Lync,” shows you how to connect in real time to other online users through instant ­messaging, voice calls, and online chats. You’ll learn how to manage transcripts, invite others to the ­conversation, and host web meetings. Chapter 12, “Designing Your ­Public Website,” shows you how to use the web tools in Office 365 to create a ­website to ­showcase your products and services and give your customers a sense of who you are and what you offer. Chapter 13, “Integrating Office 365,” presents a set of examples that show how you and your team can use the ­various tools in Office 365 together to create and share business projects.

untitled

VMware vSphere 5.0 Documentation

VMware vSphere™ 5.0 (“vSphere”) introduces many improvements and new features to extend the benefits and capabilities of vSphere 4.1. These advancements build on the core capacities in vSphere to provide improved scalability; better performance; and easier provisioning, monitoring and troubleshooting. This paper focuses on the following new features and enhancements:

• Virtual machine enhancements
• Improved SSD handling and optimization
• Command-line enhancements
• VMware® ESXi™ firewall
• vSphere Image Builder
• vSphere Auto Deploy server
• vSphere Host Profiles
• VMware vCenter™ Update Manager

The “Exchange Server 2010 Technical Video Series” on TechCenter

The Microsoft Exchange team has produced a new portfolio of videos designed to give customers a fundamental technical education on Exchange Server 2010.

The objective of the video series is to provide an introductory curriculum for IT professionals to learn more about the benefits of Exchange Server 2010. While TechNet provides great technical documentation at a more granular level, this video series should help bridge the gap for those who are new to Exchange 2010 and still trying to learn about the technical fundamentals of the product.

Each video runs 20-30 minutes long and includes an overview of the workload as well as a technical demonstration of 3-4 core scenarios related to that workload. The “Exchange Server 2010 Technical Video Series” is hosted by Ann Vu and presented by subject matter experts from the Microsoft Exchange team.

The Video’s can you find HERE.