Solution:
Restore-StorageGroupCopy won’t work because it is public folder database.

Setting a Vink by Do not Mount this Database at Startup.

En give the active clustered mailbox server a  reboot. Then Cluster service will show that the other node is going online. Then the public folder is back online. After every reboot you must start to check if the public folder online is?

Related posts

• No related posts.

Here is a list of the just some of technologies that this book talks about to achieve a Least Privilege Security:

• Program Compatibility Wizard
• Applications Compatibility Wizard
• User Account Control
• Group Policy Software Deployment
• Internet Explorer Add-on Management
• Troubleshooting Remote Users
• Configuring Windows Firewall
• Software Restrictions Policies and AppLocker
• Microsoft Deployment Toolkit
• CD Burning
• ActiveX Controls
• Changing system time and time zones
• Power Management
• Managing networks
• Standard Users Analyzer
• Applications Compatibility Toolkit
• Logon Scripts
• Remote Desktop Services
• App-V
• Med-V

I have read already some chapters. I think it is a great book to have on your collection.
You have always not enough time thinking about security. This book does it for you.

As a special offer Packt Publishing are also letting people download preview chapter of this book by download here Chapter No. 3 – Solving Least privilege Problems with the Application Compatibility Toolkit

Related posts

• No related posts.

When you try to delete the default database you will get this message:

The Database is not empty, even though it does look empty if you do a get-mailbox for the specific database:

get-mailbox -Database "Mailbox Database 1905367170"

There is a switch that you should use if you want to see all mailboxes, even the “hidden” Arbitration mailboxes:

get-mailbox -Database "Mailbox Database 1905367170" –Arbitration

This gives a different result.

As you can se the database is n’t as empty as we first thought. To move these mailboxes to the new database you can easily pipe the result of the get-mailbox command and create new move requests for all Arbitration mailboxes:

get-mailbox -Database "Mailbox Database 1905367170" -Arbitration | New-MoveRequest –TargetDatabase "MailboxDatabase1"

Related posts

• No related posts.

So I created a small visual basis script that i used as a startup script.

It checks if adsnapins.txt exist in the program files files. If exsist do nothing if it don’t exsist enable the feature.

Windows7ADSnapIns.vbs

‘Installeerd Windows 7 AD Management Snapins.
’13-07-2010 Ward Vissers

Set fso = CreateObject("Scripting.FileSystemObject")

If Not (fso.FileExists("C:\Program Files\adsnapins.txt")) Then
    Dim Wsh
    Set wsh = CreateObject("WScript.Shell")
    wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools", ,1
    wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles", ,1
    wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD", ,1
    wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS", ,1
    wsh.run "dism /online /enable-feature /featurename:RemoteServerAdministrationTools-Roles-AD-DS-SnapIns", ,1
    fso.CopyFile "\\ad.local\afs\install\Windows7Feature\adsnapins.txt", "C:\Program Files\adsnapins.txt"

End If

Set fso = Nothing

Related posts

• No related posts.

Microsoft Deployment Toolkit 2010 has some nice improvements to handle drivers. I will describe how I like to manage drivers in MDT 2010.

Some time I wrote i article about how to get the Name & Model from a computer. This is very important when you want to import only the right drivers automatically.

First we have to build the ‘Out-of-Box Drivers’ folder structure and import drivers. I have subdirectories for each architecture, brand and model.  This is what my folder tree looks like:

However, you can build your own structure, as long as you respect the proper model & brand (make) name of the vendors.

Build Out-of-Box Drivers tree

To build up the folder structure you have to know the model name of your hardware. To retrieve the proper computer name execute at powershell command prompt: ‘Get-WmiObject -Class win32_computersystemproduct | fl Name,Model,UUID,Identifyingnumber,Vendor’, to get the exact name WMI queries to determine the computer model. In my case the computer name is “Latitude D830”.

Now that we have drivers imported in our Deployment Share, it’s time to move on.

1. DriverGroups

DriverGroups existed in MDT 2008 already, although the MDT Team added subdirectory support in MDT 2010.

At deployment phase MDT uses WMI to query the proper computer model and only the current model drivers will be injected. In order to get this working properly, you have to use the EXACT model name in your Out-of-Box Driver tree.

Inject the correct drivers in your Task Sequence

Add a new step in your Task Sequence to inject the correct drivers. MDT will query the computer name and inject the drivers which corresponds with the computer name from the Out-of-Box folder structure, right before applying the image at deployment.

I use ‘DriverGroup_001’ as Task Sequence Variable, and Win7×64\%Make%\%Model% as value for my Windows 7 x64. You have to adapt this to your Out-of-Box tree.

As I use a DriverGroup I’ve disabled the ‘Inject Drivers’ task.

Customsettings.ini

As my Task Sequence handles everything, there isn’t anything needed here.

If you don’t like to use a new Task in your TS, you can add DriverGroup variables in customsettings.ini like this:

DriverGroup_001=%Make%\%Model%

DriverGroup_002=Printers

2. Selection Profiles

New in MDT 2010 are DriverSelectionProfiles. These are easy for new MDT admins, very straight forward and easy to use.

Overview:

First you have to create a Profile (or use one of the default profiles):

You can even select Packages and Applications, use it for “bad drivers” aka driver setup packs.

Select what drivers you want to add to the profile;

After making the profiles you can use them in your Task Sequences. The default ‘Inject Drivers’ settings are on the left, the customized one on the right:

You can add  Selection Profiles for drivers/packages or whatever you want. Just add an extra step in your task sequence like above.

Customsettings.ini

As with DriverGroups you can choose to handle the DriverSelectionProfile in customsettings.ini or in your TS.

Example:

DriverSelectionProfile=Dell Latitude D520 x64

Related posts

• No related posts.

1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
2. Right-click the default Web site, point to New, and then click Virtual Directory.
3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
    
4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
   
5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
    
6. Verify that the IISADMPWD virtual directory has only basic authentication is set
   
7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
    
8. Register the IISpwchg.dll file in the Iisadmpwd directory:
   Click Start, and then click Run.
   In the Open box, type the following, and then press ENTER:
   regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
   Click Start, and then click Run.
   In the Open box, type cmd, and then press ENTER.
   Locate the C:\Inetpub\Adminscripts directory.
   Type the following command, and then press ENTER:
   cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

   0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
   1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
   2: This value disables the Password Change functionality.
   4: This value disables the advance notification of password expiration.

10. Do not forget to enable Active Server Pages.
     
    Source http://support.microsoft.com/kb/297121

Related posts

• No related posts.

Index:
1) Virtualization is MORE than just VDI
2) Why storage matters
3) 3 Issues to address
4) What is IOPS and why does it matter?
5) The dumbest thing you can do
6) The secret to desktop virtualization savings
7) How the *@&% is it possible for multiple users to share the same disk image?
How Win7 will affect your storage and virtualdesktop environment 
9) Does the storage protocol matter?
10) Multiple classes of storage are okay
11) Ten questions to ask when evaluating your storage vendor
12) "TCO" and "ROI" Confusion
13) Why VDI?
14) 5 sure-fire ways to get canned
15) Which kind of virtualizer are you?
16) Why do people like VDI?
17) The Vicious Cycle of VDI storage
18) Notes for article “Desktop VM sizing & IOPS”

Just Click on the picture to go to the NetApp site where you can download this free eBook

If you click HERE you have the PDF file direct

Related posts

• No related posts.

Installation and Deployment

• VMware ESX. VMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture.
  • VMware recommends that customers start transitioning to the ESXi architecture when deploying VMware vSphere 4.1.
  • VMware will continue to provide technical support for VMware ESX according to the VMware vSphere support policy.
  • To learn more about the ESXi architecture and how to migrate from ESX to ESXi, go to the VMware ESX to ESXi Upgrade Center.
• Scripted Install for ESXi. Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network by using PXE booting. You cannot use scripted installation to install ESXi to a USB device. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.
• vSphere Client Removal from ESX/ESXi Builds. For ESX and ESXi, the vSphere Client is available for download from the VMware Web site. It is no longer packaged with builds of ESX and ESXi. After installing ESX and ESXi, users are directed to the download page on the VMware Web site to get the compatible vSphere Client for that release. The vSphere Client is still packaged with builds of vCenter Server. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.

Storage

• Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot. See the iSCSI SAN Configuration Guide and the Fibre Channel SAN Configuration Guide.
• Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Storage Performance Statistics. vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New VMDK and datastore statistics are included. All statistics are available through the vSphere SDK. See the vSphere Datacenter Administration Guide.
• Storage I/O Control. This feature provides quality-of-service capabilities for storage I/O in the form of I/O shares and limits that are enforced across all virtual machines accessing a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion. See the vSphere Resource Management Guide.
• iSCSI Hardware Offloads. vSphere 4.1 enables 10Gb iSCSI hardware offloads (Broadcom 57711) and 1Gb iSCSI hardware offloads (Broadcom 5709). See the ESX Configuration Guide, the ESXi Configuration Guide, and the iSCSI SAN Configuration Guide.
• NFS Performance Enhancements. Networking performance for NFS has been optimized to improve throughput and reduce CPU usage. See the ESX Configuration Guide and the ESXi Configuration Guide.

Network

• Network I/O Control. Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic (vNetwork Distributed Switch only). See the ESX Configuration Guide and the ESXi Configuration Guide.
• IPv6 Enhancements. IPv6 in ESX supports Internet Protocol Security (IPsec) with manual keying. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Load-Based Teaming. vSphere 4.1 allows dynamic adjustment of the teaming algorithm so that the load is always balanced across a team of physical adapters on a vNetwork Distributed Switch. See the ESX Configuration Guide and the ESXi Configuration Guide.
• E1000 vNIC Enhancements. E1000 vNIC supports jumbo frames in vSphere 4.1. See the ESX Configuration Guide and the ESXi Configuration Guide.

Availability

• Windows Failover Clustering with VMware HA. Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA. See Setup for Failover Clustering and Microsoft Cluster Service.
• VMware HA Scalability Improvements. VMware HA has the same limits for virtual machines per host, hosts per cluster, and virtual machines per cluster as vSphere. See Configuration Maximums for VMware vSphere 4.1 for details about the limitations for this release.
• VMware HA Healthcheck and Operational Status. The VMware HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status. This window displays more information about the current VMware HA operational status, including the specific status and errors for each host in the VMware HA cluster. See the vSphere Availability Guide.
• VMware Fault Tolerance (FT) Enhancements. vSphere 4.1 introduces an FT-specific versioning-control mechanism that allows the Primary and Secondary VMs to run on FT-compatible hosts at different but compatible patch levels. vSphere 4.1 differentiates between events that are logged for a Primary VM and those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT-enabled virtual machines are deployed in a cluster, allowing for cluster maintenance operations without turning off FT. See the vSphere Availability Guide.
• DRS Interoperability for VMware HA and Fault Tolerance (FT). FT-enabled virtual machines can take advantage of DRS functionality for load balancing and initial placement. In addition, VMware HA and DRS are tightly integrated, which allows VMware HA to restart virtual machines in more situations. See the vSphere Availability Guide.
• Enhanced Network Logging Performance. Fault Tolerance (FT) network logging performance allows improved throughput and reduced CPU usage. In addition, you can use vmxnet3 vNICs in FT-enabled virtual machines. See the vSphere Availability Guide.
• Concurrent VMware Data Recovery Sessions. vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances. See the VMware Data Recovery Administration Guide.
• vStorage APIs for Data Protection (VADP) Enhancements. VADP now offers VSS quiescing support for Windows Server 2008 and Windows Server 2008 R2 servers. This enables application-consistent backup and restore operations for Windows Server 2008 and Windows Server 2008 R2 applications.

Management

• vCLI Enhancements. vCLI adds options for SCSI, VAAI, network, and virtual machine control, including the ability to terminate an unresponsive virtual machine. In addition, vSphere 4.1 provides controls that allow you to log vCLI activity. See the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Command-Line Interface Reference.
• Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted. See the ESXi Configuration Guide.
• Access Virtual Machine Serial Ports Over the Network. You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring. See the vSphere Virtual Machine Administration Guide.
• vCenter Converter Hyper-V Import. vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination. See the vCenter Converter Installation and Administration Guide.
• Enhancements to Host Profiles. You can use Host Profiles to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Unattended Authentication in vSphere Management Assistant (vMA). vMA 4.1 offers improved authentication capability, including integration with Active Directory and commands to configure the connection. See VMware vSphere Management Assistant.
• Updated Deployment Environment in vSphere Management Assistant (vMA). The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS. See VMware vSphere Management Assistant.
• vCenter Orchestrator 64-bit Support. vCenter Orchestrator 4.1 provides a client and server for 64-bit installations, with an optional 32-bit client. The performance of the Orchestrator server on 64-bit installations is greatly enhanced, as compared to running the server on a 32-bit machine. See the vCenter Orchestrator Installation and Configuration Guide.
• Improved Support for Handling Recalled Patches in vCenter Update Manager. Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed. See the vCenter Update Manager Installation and Administration Guide.
• License Reporting Manager. The License Reporting Manager provides a centralized interface for all license keys for vSphere 4.1 products in a virtual IT infrastructure and their respective usage. You can view and generate reports on license keys and usage for different time periods with the License Reporting Manager. A historical record of the utilization per license key is maintained in the vCenter Server database. See the vSphere Datacenter Administration Guide.
• Power Management Improvements. ESX 4.1 takes advantage of deep sleep states to further reduce power consumption during idle periods. The vSphere Client has a simple user interface that allows you to choose one of four host power management policies. In addition, you can view the history of host power consumption and power cap information on the vSphere Client Performance tab on newer platforms with integrated power meters. See the vSphere Datacenter Administration Guide.

Platform Enhancements

• Performance and Scalability Improvements. vSphere 4.1 includes numerous enhancements that increase performance and scalability.
  • vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
  • New optimizations have been implemented for AMD-V and Intel VT-x architectures, while memory utilization efficiency has been improved still further using Memory Compression. Storage enhancements have led to significant performance improvements in NFS environments. VDI operations, virtual machine provisioning and power operations, and vMotion have enhanced performance as well.

  See Configuration Maximums for VMware vSphere 4.1.

• Reduced Overhead Memory. vSphere 4.1 reduces the amount of overhead memory required, especially when running large virtual machines on systems with CPUs that provide hardware MMU support (AMD RVI or Intel EPT).
• DRS Virtual Machine Host Affinity Rules. DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons. See the vSphere Resource Management Guide.
• Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk. See the vSphere Resource Management Guide.
• vMotion Enhancements. In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively). See the vSphere Datacenter Administration Guide.
• ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine. You can configure a virtual machine to use USB devices that are connected to an ESX/ESXi host where the virtual machine is running. The connection is maintained even if you migrate the virtual machine using vMotion. See the vSphere Virtual Machine Administration Guide.
• Improvements in Enhanced vMotion Compatibility. vSphere 4.1 includes an AMD Opteron Gen. 3 (no 3DNow!™) EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and the reduced need to restart virtual machines. See the vSphere Datacenter Administration Guide.

Partner Ecosystem

• vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC’s ESX PowerPath Module. vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC’s PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale. See the vCenter Update Manager Installation and Administration Guide.
• User-configurable Number of Virtual CPUs per Virtual Socket. You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket. See the vSphere Virtual Machine Administration Guide.
• Expanded List of Supported Processors. The list of supported processors has been expanded for ESX 4.1. To determine which processors are compatible with this release, use the Hardware Compatibility Guide. Among the supported processors is the Intel Xeon 7500 Series processor, code-named Nehalem-EX (up to 8 sockets).

You can download VMware vSphere 4.1 HERE

Related posts

• No related posts.

It’s a great tool im loving it.

What new:

For System Center Configuration Manager 2007 users:

• New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.

• Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.

For Lite Touch Installation:

• Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
• Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.

Bug Fixes and small improvements

• LTI Wizard performance improvement. The LTI Wizard now takes less time to initialize and shows up faster.
• Issue in validating connection to the server fixed. In a few scenarios, MDT 2010 used to report the error message, "A connection to the distribution share could not be made" when a task sequence is run. The Microsoft Support article, “Error message when you use MDT 2010: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed,’” at http://support.microsoft.com/kb/977566 describes this issue in detail. This issue has been fixed in MDT 2010 Update 1.
• Support for installing Windows 7 roles and features. MDT 2010 Update 1 adds support for installation of Windows 7 operating system roles and features.
• Looping issue with x64 custom Windows images fixed. In MDT 2010, ZTI–System Center Configuration Manager deployments could get into an infinite loop when deploying an x64 Windows image captured by LTI. This issue has been fixed in MDT 2010 Update 1
• Error handling improvements in MDT task sequence templates. In MDT 2010, task sequences appear to finish successfully even when they really failed. These issues are fixed in MDT 2010 Update 1.

Download the new version HERE

Related posts

• No related posts.

Doing some Canyoing, Walking, Moutainbiking, Climbing & Abseiling.

It is was a nice ten day’s.

Next monday it is my first workday after holiday again. Soon I will start blogging again.
First few days rest.

Related posts

• No related posts.

Related posts

• No related posts.

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.

Step 9. Use Group Policy to set the language settings for users

1. Download the Office 2010 policy template files to your computer. You will find them HERE

2. Make a new GPO named Office 2010 languages settings it is a user policy.

3. Under User Configuration in the console tree, right-click Administrative Templates.

4. Click Add/Remove Templates, and then click Add.

5. In the Policy Templates dialog box, click the template that you want to add, and then click Open.

6. After you add the Office 2010 templates, click Close.

7. Open the Group Policy object (GPO) for which you want to set policy.

8. Double-click User Configuration and expand the tree under Administrative Templates.

9. Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.

10. Select the languages that you want to use for each setting.

11. Save the GPO.

12. Go Testing

Related posts

• No related posts.

Windows Server 2008 R2 Support

Exchange Server 2007 SP3 supports all Exchange 2007 roles on the Windows Server 2008 R2 operating system.

Windows 7 Support

Exchange 2007 SP3 supports the installation of the Exchange 2007 management tools on a computer that is running Windows 7. Additionally, Exchange 2007 SP3 provides support for the installation of the Exchange 2007 Management Tools together with the Exchange Server 2010 Management Tools on the same Windows 7-based computer.

Improved Password Reset Functionality

Exchange 2007 SP3 introduces password reset functionality for Internet Information Services (IIS) 7.

To enable the password reset feature

1. Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.

2. Start Registry Editor, and then locate the following registry subkey:

   HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

3. Create the following DWORD value if it does not already exist:

   Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1

4. Exit Registry Editor.

 Updated Search Functionality

Exchange 2007 SP3 includes updates to the Exchange Search (MSSearch) component. MSSearch provides support for creating full text indexes for Exchange stores. Exchange 2007 SP3 updates the MSSearch binary files to MSSearch 3.1.

Schema Changes

Exchange 2007 SP3 includes Active Directory schema changes for certain Unified Messaging (UM) mailbox attributes. For more information, see Active Directory Schema Changes (SP3).

Support for Right-to-Left Disclaimer Text

Exchange 2007 SP3 includes support for Right-to-Left text in e-mail message disclaimers in a right-to-left language, such as Arabic. In earlier versions of Exchange, when you use a transport rule to create a disclaimer in a right-to-left language on an Exchange 2007 Hub Transport server, the text appears incorrectly when you view it from Outlook 2007.

Exchange 2007 SP3 adds functionality to the transport rule setting to fully support right-to-left text in disclaimers.

Download here SP3 for Exchange 2007

Related posts

• No related posts.

Configuration:

Server 1 – HYPERVDC-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.90
Roles: Active Directory / Hyper-V

Server 2 – CHEK10-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.91
Roles: Exchange 2010 HT / CAS

Server 3 – CHEK10-02
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.92
Roles: Exchange 2010 HT / CAS

Server 4 – DAGEK10-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.93
Roles: Exchange 2010 MBX

Server 5 – DAGEK10-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.94
Roles: Exchange 2010 MBX

Creating the DAG

Groupname: DAG01
Witness Server: CHKEK10-01 (Microsoft says use one of the CAS or Hub Servers. You cannot use a DAG Server! If you want use a non Exchange 2010 server you must at the Exchange Trusted Subsystem group at the local administrators group.
Witness Directory: C:\DAG01

Add a MB server to a DAG

Setting a IP address on a Database Availability Group

With the following command you can set the DAG Database Availability Group an IP address. Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 192.168.150.96

Related posts

• No related posts.

KB 982639 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out starting with 5 improvements we made to prevent crashes in very unique scenarios.

• KB 980852 The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
• KB 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
• KB 980364 The Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
• KB 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
• KB 979790 An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox

We corrected a few replication issues some of you encountered.

• KB 980149 The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
• KB 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
• KB 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server

Important:
Microsoft Update does not detect Update rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG).

Download Rollup 4 for Exchange 2010 HERE

Related posts

• No related posts.

Office is not activated

Determining Which Activation Method Office is Using – KMS or MAK

Click the start menu and enter cmd /k cscript “%programfiles%\Microsoft Office\Office14\ospp.vbs” /dstatus in the search box.

If running 32 bit Office 2010 on 64 bit Windows, %programfiles% above should be replaced with %programfiles(x86)%.

Not Activated

Checking if a DNS Domain is Configured for KMS Auto-Discovery

To check if a DNS domain is configured for KMS auto-discovery, check that a SRV record exists.

nslookup -type=srv _vlmcs._tcp.wardvissers.nl

If a SRV record exists for the domain, the DNS server will detail the SRV record.

C:\>nslookup -type=srv _vlmcs._tcp

Server:  ward-dc02.wardvissers.local

Address:  192.168.150.6

Non-authoritative answer:

_vlmcs._tcp.wardvissers.local SRV service location:

          priority       = 0

          weight         = 0

          port           = 1688

          svr hostname   = ward-dc2.wardvissers.local

If no SRV record exists for the domain, the DNS server will return an error

Verifying that a Windows Computer can Communicate with the KMS Activation Server

KMS activation requires that the machine to be activated has TCP port 1688 open for outbound communication to the activation server.

Verifying that outbound TCP port 1688 is open to the KMS server

1. Download and install the utility portqry.exe from Microsoft. It is a command line utility from Microsoft that reports the port status of a remote host.
2. From a command prompt, run the command:

portqry.exe -n ward-dc02.wardvissers.local -p tcp -e 1688

The command will return “TCP port 1688 (unknown service): LISTENING” if the computer is able to communicate with the KMS server.

If the command returns “TCP port 1688 (unknown service): FILTERED” then the computer is unable to communicate with the KMS server

Manually Specifying the KMS Activation Server

1. Type cmd in the search bar to locate the command window..
2. At the command prompt, type cd\Program Files\Microsoft Office\Office14.

If running 32 bit Office 2010 on 64 bit Windows, Program Files above should be replaced with Program Files (x86).
Run the command cscript ospp.vbs /sethst:ward-dc02.wardvissers.local to manually specify the KMS activation server.

Run the command cscript ospp.vbs /act to activate Office with the KMS server.

Launch Microsoft Outlook 2010 agein
Click to the File tab. Click Help.

Office is activated

Related posts

• No related posts.

Click on the picture to download the pdf.

Source

Related posts

• No related posts.

MDT 2010 creates the following log files:

BDD.log: This is the aggregated MDT 2010 log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file.

LiteTouch.log: This file is created during LTI deployments. It resides in %WINDIR%\TEMP\DeploymentLogs unless you specify the /debug:true option.

Scriptname.log: This file is created by each MDT 2010 script. Scriptname represents the name of the script in question.

SMSTS.log: This file is created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, or C:\_SMSTaskSequence, or C:\SMSTSLog.

Wizard.log: The deployment wizards create and update this file. 

WPEinit.log: This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE.

DeploymentWorkbench_id.log: This log file is created in the %temp% folder when you specify a /debug when starting the Deployment Workbench.

Related posts

• No related posts.

I haven’t any pre-Created CAS arrays in my hyper-v.local domain. But you would to check of there is any pre-created CAS Arrays. Run the command below. if you didn’t create a CAS Array before, you will get nothing .

Get-ClientAccessArray

Then you should create new Client Access Array. Run below Cmdlet in Exchange Management Console

New-ClientAccessArray –Name “CasArray1” –Fqdn casarray.hyper-v.local -Site “Default-First-Site-Name”


Now we have finished creating a CAS array. Then we must associate databases with this CAS Array.
Use below CMDLet to add mailbox database to CAS array. We can attach all mailbox databases at once as shown as shown  below

Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “casarray.hyper-v.local”

Related posts

• No related posts.

Microsoft Download Center Link is here and direct downloadable exe file link is available below.

File Name: Exchange2010-SP1-Beta-x64.exe
Version: 14.01.0180.002
Date Published: 6/5/2010
Language: English
Download Size: 532.5 MB

Related posts

• No related posts.

You need two or more Exchange 2010 servers (each with two NICs) with the CAS role installed have been deployed, you are ready to start configuring NLB to provide high availability and load balancing.  First, you must allocate a dedicated private IP address and create an associated A record in DNS for the NLB cluster. 

This IP address and name are what clients will connect to and against which the ClientAccessArray will be created.  In this blog post, I will use 192.168.150.95 and casarray.hyper-v.local
To simplify the management of your NLB cluster members, I recommend that you name each NIC’s network connection so that it is easy to understand what function the NIC serves.  For example, as depicted below, I have named the connections “LAN” (used for communication with clients and servers on the network) and “NLB” (used for internal NLB heartbeat).  This process should be repeated on all NLB cluster members.

IP configuration:
Server 1:
LAN:
IP: 192.168.150.90
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Server 2:
LAN:
IP: 192.168.150.91
Subnetmask: 255.255.255.0
Gateway: 192.168.150.254
DNS: 192.168.150.1

Configuring NLB – First Member

On each NLB cluster member, NLB must be installed.  With Windows 2008 R2, this can be completed simply by running the command “ServerManagerCmd -i NLB” via a command prompt.  Once NLB has been installed, launch the Network Load Balancing Manager to continue the configuration process.

To create your new cluster, you can right-click Network Load Balancing Clusters or simply click Cluster, New.  In the New Cluster wizard, enter the name of the first server in the NLB cluster (for example, CHEK10-01) and click Connect.  This will display the available NICs on the server, at which point the NLB NIC should be chosen before clicking Next.

Since this is the first member of the NLB cluster, you can leave the all of the Host Parameters at their default values, as depicted below.  Please note that the Priority value should be configured as 1 for the first member.

Next we must configure the IP address and subnet mask of the NLB cluster, which is the IP address for which we created a DNS A record at the very beginning of this process.  In this example, this would be 192.168.150.95 and 255.255.255.0, respectively.

For the Cluster Parameters, we want to enter the FQDN of the DNS A record we created at the very beginning of this process (casarray.hyper-v.local).  In addition, Unicast should be selected as the desired clustered operation mode.

I lieve the Port Rules how they are and end with Finish

Let the NLB cluster converge with its first member and you should eventually see the cluster report success.

Now you can proceed with adding your second cluster member.

Configuring NLB – Second/Subsequent Member

After the configuration of the NLB cluster itself and the first NLB cluster member has been completed, you are ready to add additional members.  Provided that NLB has been installed, you can simply right-click on your NLB cluster in the Network Load Balancing Manager and click Add Host To Cluster.

Enter the name of the second NLB cluster member, for example CHEK10-02, and click Connect.  Be sure to choose the NLB LAN NIC and click Next.

On the Host Parameters screen, ensure that the Priority is set to 2 (or as appropriate, depending on how many cluster members you have) and click Next.

Confirm that your port rules are accurate and, if they are, click Finish to add your second NLB cluster member.

Let the NLB cluster converge with the new member and, eventually, it should report success.

At this point, you have an NLB cluster with two members!

Next configure CASARRAY.

Related posts

• No related posts.

Related posts

• No related posts.

Additionally, when you open the TPM Management Console and you try to initialize TPM you get error message 0×80070005.

Solution:

To set correct permissions, follow the instruction below:

1. Open Active Directory Users and Computers.

2. Select the OU where you have all computers which will have Bitlocker turned ON.

3. Right Click on the OU and click Delegate Control.

4. Click Next and then click Add.

5. Type SELF as the Object Name.

6. Select create a custom task to delegate.

7. From the object in the folder, select Computer Objects.

8. Under show these permissions, select all 3 checkbox.

9. Scroll down in permissions and select the attribute Write msTPM-OwnerInformation.

10. Click Finish.

After you have done the above steps, you should be able to initialize TPM successfully.

It worked for me!!!

SOURCE

Related posts

• No related posts.

2. Go to the Tab Advanced

3. Set V by Hide group from Exchange address list

Related posts

• No related posts.

1) Manage your current server certificates.
2) Enable certificates for Exchange 2007 Services (POP, IMAP, SMTP, IIS, UM).
3) Generate an Exchange 2007 Certificate Signing Request and process the Certificate Authority answer.
4) Generate an Exchange 2007 Self-Signed certificate (not for production use).
5) Easily include additional subject names in a single certificate.
6) Import & Export ability for existing certificates.
To read more about Certificate Use in Exchange 2007 at Microsoft TechNet follow the link:

Certificate Manager for Exchange Server 2007 is currently offered by U-BTech Solutions free of charge

Certificate Manager for Exchange Server 2007 Flash Demonstration

Download – Certificate Manager for Exchange 2007

SOURCE

Related posts

• No related posts.