Tag: Server 2008

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1).

Error:
The following alert became inactive at 27-9-2011 3:15:52.

Status: Inactive

Data source type:

Data source: System Protection

Computer: <ServerName>

Description: Last 1 recovery points not created.

DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 521, WSB Error Code: 0x807800A1).

For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.

Solution:

Some noncritical volumes are included in the system state backup image when you use the "-allCritical" switch in Windows Server 2008 R2 or in Windows 7 only for non SP1 systems. SP1 includes this hotfix.

Optimizing Windows 7 Images for use in VDI

One of our MCS deployment guys in the UK – Jonathan Bennett (you may know Jonathan as the author of the autoit tools and GImageX) has developed a tool for configuring Windows 7/Windows Vista/Server 2008 images for use in a VDI environment. The tool called VDI Optimizer outputs a VBScript (based on the selections you make in the GUI interface), which can then be used to apply performance and configuration settings to images that will be deployed via VDI platforms – this is particularly useful if you are using MDT 2010 for your image engineering process as the VBScript can bolted into the task sequence using a Run Command Line task.

image

You can make machine based selections for turning off services and functions that may not be required when the operating system is running in a VDI environment such as hibernation, system restore, and background defrag, as well as adjusting some user based settings such as visual effects, font smoothing and off-screen composition for Internet Explorer.

The beta of this tool is available from http://www.autoitscript.com/files/tools/VDIOptimizer.zip but please remember The tool is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation.

Source: Optimizing Windows 7 images for use in VDI

Preventing Automatic Service Pack 1 Update to Windows 7 and Windows Server 2008 R2

Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.

Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.

Download

Download details: www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7

The tool can be used with:

  • Windows 7 Service Pack 1
  • Windows Server 2008 R2 Service Pack 1

Toolkit Components

The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.

The components are:

  • A Microsoft-signed executable
  • A script
  • An ADM template

Registry key

The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.

Key value name: DoNotAllowSP

  • When the key value name is not defined, distribution is not blocked.
  • When the key value name is set to 0, distribution is not blocked.
  • When the key value name is set to 1, distribution is blocked.

Blocker Script

The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.

When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.

When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.

Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.

Group Policy Administrative Template (.ADM file)

The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.

Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.

Windows 7 and Windows Server 2008 R2 SP1 Blocker: Group Policy Settings

Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.

Block Windows 7 and Windows Server 2008 R2 SP1 automatic updates

Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.

System Center Operations Manager 2012 Beta is released

Overview

System Center Operations Manager 2012 provides the monitoring component of cloud and datacenter solutions, to help you manage your datacenter and cloud environments by:

  • Delivering flexible and cost effective enterprise-class monitoring and diagnostics while reducing the total cost of ownership by leveraging commodity hardware, with standard configurations to monitor heterogeneous environments.
  • Helping to ensure the availability of business-critical applications and services through market-leading .NET application performance monitoring and diagnostics plus JEE application health monitoring.
  • Providing a comprehensive view of datacenters, and private and public clouds.

Feature Summary

  • Predictable performance and availability of critical applications
    • End-to-end views of application health and topology
    • Establishment of application service-level delivery (SLAs)
    • Precise identification of application errors
  • Flexible and cost-effective infrastructure monitoring
    • In-depth monitoring, diagnostics, and reporting for heterogeneous environments
    • Integrated network device monitoring and alerts
    • Simplified management infrastructure
  • Comprehensive monitoring for your datacenter and cloud—on your terms
    • Integrated physical, virtual, and cloud management
    • Common console across datacenter and clouds
    • Rich reporting

System requirements

Supported Operating Systems: Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2, Windows XP Service Pack 3

  • Other Software:
    • Any server role
      • .NET 3.5 or 4.0
    • Management Server, Reporting Server, Web Console, Gateway Server
      • Windows Server 2008 R2 (64 bit)
    • Operational & Data Warehouse
      • SQL 2008 SP1 and above
      • SQL Collation – SQL_Latin1_General_CP1_CI_AS
    • Agent
      • Windows Server 2003 SP2 and above
      • Windows Server 2008 SP2 and above
      • Windows Server 2008 R2
      • Windows XP Professional SP3 and above
      • Windows Vista SP2 and above
      • Windows 7

    Supported Hardware Configuration:

    • Operations Manager Operations database: 4 GB of RAM or higher, 50 GB of available hard disk space
    • Management server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Operations console: 2 GB of RAM or more, 20 GB of available hard disk space
    • Reporting data warehouse: 4 GB of RAM or more, 100 GB of available hard disk space
    • Reporting server: 2 GB or more, 20 GB of available hard disk space
    • gateway server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Web console server: 2 GB of RAM or more, 20 GB of available hard disk space
    • Audit database: 4 GB of RAM or more, 100 GB of available hard disk space
    • Management server with audit collector: 2 GB of RAM or more, 50 GB of available hard disk space
    • Management server with Agentless Exception Monitoring file share: 2 GB of RAM or more, 30 GB of available hard disk space
    • Agent: Please refer to the recommended hardware requirement required by the operating system.

Download the beta HERE

System Center Data Protection Manager 2010 Doesn’t Detect Tape Drives In Library

I’ve used System Center Data Protection Manager (DPM) since the 2007 beta, primarily for SharePoint and SQL backups & Exchange Backups.  At a customer they have one  DPM server which backs up to disk and additionally to a HP MSL2024 Tape Library for long term protection. The runs Windows Server 2008 R2 with DPM 2010 since its release.

After updating de DPM Server with SP1 for Windows 2008 R2 en updated the drivers. I had some issues with DPM. What I found was that although DPM installed correctly it couldn’t see  all the tape drives in the VTL. All the tape drives were visible in Device Manager and none were showing errors. I use the RECOMMENDED * HP StorageWorks Tape Drivers for Windows

In the DPM console under Management -> Libraries, the library was listed, but Total Drives was 0, rather than the expected 2. The DPM console showed the following error:

image

I followed the instructions to remap the drives here: http://technet.microsoft.com/en-us/library/bb795782.aspx. The DPMLA.xml file produced by the tool was correct, showing the correct SCSI IDs, serial numbers etc. but DPM still couldn’t see the drives.

I found the solution to the problem on the DPM forum here: http://social.technet.microsoft.com/Forums/en-US/dpmtapebackuprecovery/thread/1d599443-7bf6-437a-bf12-52847fa7c8e5/ What I did is update the tape drive driver to the Inbox LTO driver as described on the forum and below:

1) Open device manager
2) Locate the tape drive
3) Right-click and look at the properties.
3) Under the DRIVER tab, select UPDATE DRIVER
a) Select the Install from list or specific location (Advanvced) – next.
b) Select Don’t search. I will choose the driver to install. – next.
c) Uncheck the Show comtabile hardware checkbox.
d) Highlight LTO under the manufacturer.
e) Highlight the LTO tape drive under model – then next.
f) This should install the Microsoft ltotape.sys driver.
4) Rescan the tape library in the DPM console – try to take another backup.

After following the above steps, all the two tape drives were visible in the DPM console.

Microsoft Office 365 Deployment Readiness Tool

The Office 365 Deployment Readiness Tool provides analysis of your on-premises environment in preparation for an Office 365 enterprise deployment. The readiness tool is integrated with the guidance provided in the web edition of the Microsoft Office 365 Beta Deployment Guide.

Download HERE

I run the tool in my test environment. See below the results

Microsoft Office 365 Deployment Readiness Tool

Beta

Office 365 Deployment Resource Kit build 01.00.00.00
modgClick here for the Microsoft Office 365 Beta Deployment Guide for Enterprises

Domains

modg Deployment Guide: Adding Your Domain(s) to Office 365
All email domains discovered in your environment:
Total: 3

All primary email domains discovered:
Total: 2

Primary email domain suffixes with greater than 50 users:
wardvissers.local
Total: 1


User Identity and Account Provisioning

Active Directory

Statistics

Total number of domains discovered in your forest: 1
Estimated total number of users: 59
Estimated total number of contacts: 0
Estimated total number of groups: 54
Estimated total number of mailboxes: 53
Estimated total number of objects for Directory Synchronization: 113
note
Note: Filters were applied to obtain the above object counts for an Office 365 deployment.

Forest and Domains

The following domains were discovered in your Active Directory forest:
wardvissers.local
Total: 1

Trusts

No forest trusts found
green
You may deploy AD FS 2.0 and Directory Synchronization without multi-forest constraints

Schema and Forest/Domain Functionality Levels

Active Directory forest schema level: Windows Server 2008 R2
Exchange schema level: Exchange Server 2010 SP1
Domain Functionality:Windows Server 2008 R2
Forest Functionality:Windows Server 2008 R2
Domain Controller Functionality:Windows Server 2008 R2
green
It appears that your Active Directory schema is prepared for Exchange Rich Coexistence
modg Deployment Guide: Exchange Rich Coexistence Requirements


Active Directory Cleanup

modg Deployment Guide: Active Directory Cleanup

samaccountname (user name) Attribute

green
Character length test passed
green
Unsupported character test passed

givenname (first name) Attribute

green
Character length test passed
green
Unsupported character test passed

sn (last name) Attribute

green
Character length test passed
green
Unsupported character test passed

displayname Attribute

green
Character length test passed
green
Unsupported character test passed

mail (email address) Attribute

green
Character length test passed
green
Unsupported character test passed
green
No duplicates found

mailnickname Attribute

green
Character length test passed
green
Unsupported character test passed

proxyaddresses (email addresses) Attribute

green
No duplicates found
green
Unsupported character test passed

Directory Synchronization

Object count assessment:
Estimated number of objects for Directory Synchronization (entire forest): 113
modg Deployment Guide: Object Count Considerations
Enterprise Admin rights:
green
It appears that you are an enterprise admin
Directory Synchronization admin requirement met!
modg Deployment Guide: Directory Synchronization Required Permissions
Active Directory recycle bin:
warning
Active Directory recycle bin is enabled in your forest this may impact your total object count quota for Directory Synchronization.


Office 365 Single Sign On and Identity

AD FS 2.0 Directory Cleanup Check:

UserPrincipalName (logon ID for Office 365) Attribute

fyi
Update values once you have verified your organization does not have any other application dependencies on the UserPrincipalName attribute.
modg Deployment Guide: Active Directory Cleanup
green
Unsupported characters test passed
green
Spaces in logon value test passed
green
Unicode character test passed
note
Note: All Unicode characters will be converted to underscores (_) in the UserPrincipalName field.
green
No UserPrincipalName duplicates found
warning
Discovered users without a user logon name (blank value) for UserPrincipalName
You will need to provide each user a UserPrincipalName in order for these users to sign into Office 365.
fyi
Below is a list of your UserPrincipalName domain suffixes in use:
wardvissers.local
Total: 1
note
Note: During the Office 365 Beta only one namespace (root and child domains) per AD FS 2.0 farm
Example contoso.com and root.contoso.com would require 1 AD FS 2.0 farm and fabrikam.com would require an additional AD FS 2.0 farm

fyi
Password length per domain:

wardvissers.local = 7

Exchange Online

Discovered Exchange Server(s) on-premises:
Estimated total number of Exchange Servers: 1

Statistics:
Estimated total number of users with default mailbox size (True): 53
Estimated total number of users with larger than default mailbox size (False): 0
Estimated total number of objects with Exchange organization level quota: 6


Lync Online

Lync user assessment:
Estimated total number of users leveraging Office Communications/Lync on-premises: 2
Sip domains:
fyi
The following sip domains were discovered:
wardvissers.local
Total: 1

SharePoint Online

User object count assessment:
green
The number of user objects in your forest is supported.
modg Deployment Guide: Object Count Considerations

Client and End User Experience

modg Deployment Guide: Rich Experience Client Requirements

Summary of client computer readiness (Office 365 single sign-on and rich client checks):

warning
Below is an estimate of computer operating systems NOT ready for Office 365 rich client experience:
Total: 0
green
Below is an estimate of computer operating systems ready for Office 365 rich client experience:
Windows XP Service Pack 3: 3
Windows 7 Service Pack 1: 3
Total: 6

Network


fyi
IP Configuration:
IPv4 Address. . . . . . . . . . . : 192.168.150.60
IPv4 Address. . . . . . . . . . . : 192.168.150.1
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Default Gateway . . . . . . . . . : 192.168.150.254

fyi
Trace route to your default gateway:
Tracing route to 192.168.150.254 over a maximum of 30 hops
1 1 ms 2 ms 2 ms 192.168.150.254

fyi
Trace Route test to Exchange Online:
Tracing route to outlook.com [65.55.94.40]
over a maximum of 30 hops:
1 3 ms 2 ms 1 ms 192.168.150.254
2 * 24 ms 25 ms 82.169.11.254
3 25 ms 26 ms 26 ms 195.69.145.20
4 145 ms 146 ms 144 ms 10.14.234.234
5 * * * Request timed out.
6 * * * Request timed out.
7 10.14.234.234 reports: Destination net unreachable.
Trace complete.
fyi

For additional tests utilize the Exchange Remote Connectivity Analyzer

Port Query Tests:

modg Deployment Guide: Ports and Protocols
green
portal.microsoft.com
Made a TCP 443 connection to portal.microsoftonline.com
green
Outlook.com
Made a TCP 443 connection to outlook.com
green
Outlook.com IMAP
Made a TCP 993 IMAP connection to outlook.com
green
Outlook.com POP
Made a TCP 995 POP connection to outlook.com
green
Outlook.com SMTP
Made a SMTP TCP 587 connection to outlook.com
green
Active Directory Federation Services End Point
Made a TCP 443 connection to nexus.microsoftonline.com
green
Directory Synchronization End Point
Made a TCP 443 connection to adminwebservice.microsoftonline.com
green
Office 365 PowerShell End Point
Made a TCP 443 connection to ps.microsoftonline.com
green
Outlook.com PowerShell End Point
Made a TCP 443 connection to ps.outlook.com
green
Office 365 Community End Point
Made a TCP 80 connection to community.office365.com
green
Lync Online SIP Connection
Made a TCP 443 connection to sipdir.online.lync.com
green
Lync Online Federation
Made a TCP 5061 connection to sipfed.online.lync.com
Domain Name System (DNS) name records checks:
fyi
Found the following MX DNS record(s):
Server: localhost
Address: 127.0.0.1
wardvissers.local
primary name server = ward-dc01.wardvissers.local
responsible mail addr = hostmaster.wardvissers.local
serial = 761
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
Information Gathered On:
WARD-DC01
Date: za 07-05-2011
Start Time: 18:19
End Time: 18:21

GAL Photos in Exchange 2010 and Outlook 2010

With Microsoft Exchange 2010 and Outlook 2010 & Lync & Sharepoint 2010 you can finally get photos into your global address list (GAL) and see just who’s who on your emails. You can do this on 2 way’s

1. Using Powershell Smile

    A minor schema change

    First stop, the AD Schema. A minor schema modification is required to flip the thumbnailPhoto attribute to make it replicate to the Global Catalog.

    1. If you haven’t registered the Schema MMC snap-in on the server you want to make this change on, go ahead and do so using the following command:

      Regsvr32 schmmgmt.dll

    2. Fire up a MMC console (Start -> Run -> MMC) and add the Schema snap-in

    3. In the Active Directory Schema snap-in, expand the Attributes node, and then locate the thumbnailPhoto attribute. (The Schema snap-in lists attributes by its ldapDisplayName).

    4. In the Properties page, select Replicate this attribute to the Global Catalog, and click OK.

      Figure 1: Modifying the thumbnailPhoto attribute to replicate it to Global Catalog

      Loading pictures into Active Directory

      Now you can start uploading pictures to Active Directory using the Import-RecipientDataProperty cmdlet, as shown in this example:

      Import-RecipientDataProperty -Identity "Ward VIssers" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\wardvissers.jpg" -Encoding Byte -ReadCount 0))

      To perform a bulk operation you can use the Get-Mailbox cmdlet with your choice of filter (or use the Get-DistributionGroupMember cmdlet if you want to do this for members of a distribution group), and pipe the mailboxes to a foreach loop. You can also retrieve the user name and path to the thumbnail picture from a CSV/TXT file.

      2. Using a Free tool like Outlook Photos from Exclaimer

      Download the Tool HERE

      The tool is easy to use Smile.

      Prerequisites

      User Preferences

        Domain user – The logged in user’ account is required to be an Active Directory account.

        Domain computer – The computer the user is logged into needs to be joined to an Active
        Directory domain.

        Active Directory permissions – The logged in user must have permission to upload photos to the required Active Directory accounts. (Alternate credentials can be supplied or control of the thumbnailPhoto field can be delegated to the logged in user.)

      Operating System

      • Windows Server 2003 x86 (including all service pack levels).
      • Windows Server 2003 R2 x86 and x64 (including all service pack levels).
      • Windows Server 2008 x86 and x64 (including all service pack levels).
      • Windows Server 2008 R2 x86 and x64 (including all service pack levels).
      • Windows Small Business Server 2003 (including all service pack levels).
      • Windows Small Business Server 2008.
      • Windows Small Business Server 2011.
      • Windows XP x86 and x64 (including all service pack levels).
      • Windows Vista x86 and x64 (including all service pack levels).
      • Windows 7 x86 and x64 (including all service pack levels).

      Other Software

      Microsoft Outlook 2010 x86 and x64

      Microsoft .NET Framework 3.5 SP1

      Microsoft Exchange 2010 RTM and above

      Active Directory

      You must be logged into an Active Directory domain to run the application.

      Active Directory Forest
      Domain and Forest functional level of Windows Server 2008 and above.
      For Domain or Forest functional level of Windows Server 2003, the Windows Server 2008 Forest preparation must first be complete.

      Screenshots

        image image

      Windows Server 2008 R2 Hyper-V SP1 Component Architecture Poster

      This poster provides a visual reference for understanding key Hyper-V technologies in Windows Server 2008 R2 Service Pack 1. It focuses on architecture, snapshots, live migration, virtual networking, storage, RemoteFX and Dynamic Memory.

      To download the poster click on the picture
      image

      System Center Virtual Machine Manager 2012 Beta Evaluation

      System Center Virtual Machine Manager 2012 delivers industry leading fabric managment, virtual machine management and services deployment in private cloud environments. Virtual Machine Manager 2012 offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.

      Feature Summary

      • Fabric Management
        • Hyper-V and Cluster Lifecycle Management – Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V Cluster
        • Third Party Virtualization Platforms – Add and Manage Citrix XenServer and VMware ESX Hosts and Clusters
        • Network Management – Manage IP Address Pools, MAC Address Pools and Load Balancers
        • Storage Management – Classify storage, Manage Storage Pools and LUNs
      • Resource Optimization
        • Dynamic Optimization – proactively balance the load of VMs across a cluster
        • Power Optimization – schedule power savings to use the right number of hosts to run your workloads – power the rest off until they are needed
        • PRO – integrate with System Center Operations Manager to respond to application-level performance monitors
      • Cloud Management
        • Abstract server, network and storage resources into private clouds
        • Delegate access to private clouds with control of capacity, capabilities and user quotas
        • Enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud
      • Service Lifecycle Management
        • Define service templates to create sets of connected virtual machines, os images and applica tion packages
        • Compose operating system images and applications during service deployment
        • Scale out the number of virtual machines in a service
        • Service performance and health monitoring integrated with System Center Operations Manager
        • Decouple OS image and application updates through image-based servicing
        • Leverage powerful application virtualization technologies such as Server App-V

      System Requirements

      • Supported Operating Systems:Windows 7 Enterprise;Windows 7 Professional;Windows 7 Ultimate;Windows Server 2008 R2;Windows Server 2008 R2 Datacenter;Windows Server 2008 R2 Enterprise
        • Windows Server 2008 R2 (full installation) Standard, Enterprise, Datacenter x64
        • Windows 7 Professional, Enterprise, Ultimate x32, x64
        • Windows Remote Management (WinRM) 2.0
        • Windows PowerShell 2.0
        • Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
        • Windows Automated Installation Kit (AIK) for Windows 7
        • SQL Server 2008 or SQL Server 2008 R2 Standard, Enterprise, and Datacenter
        • Windows Deployment Services (WDS) – (Version on Windows Server 2008 R2)
        • Windows Software Update Services (WSUS) 3.0 SP2 64bit

      Download System Center Virtual Machine Manager 2012 Beta Evaluation HERE

      Translate »