After deploying I had a unknown device – ACPI/ACPI0004/CPUSCK0

I could not find any driver. The windows device manager show still “unknown device”.

Solution:
Under: Advanced –> Bus Options you will find the setting “Legacy ACPI CPU Tables”
This settings is default disabled. Enable it en unknown device is gone!!

Windows 7 and Windows 8 Optimization Guide for Horizon View Virtual Desktops

Antivirus Best Practices for Horizon View 5.x

Modern workforces expect flexibility from their employers; users need to have the capability to work anywhere with multiple devices and a high degree of self-service. With Flex+ workspace virtualization, Immidio enables such a flexible workstyle in a simple, scalable, extensible and affordable manner, without introducing additional complexity. Immidio Flex+ uses the existing Windows infrastructure, ensuring a low total cost of ownership.

Next to many small improvements, the latest version of Immidio Flex+ contains new features that were mostly developed based on feedback from Immidio’s partners and customers. The focus of this release is to support the latest Windows versions and application virtualization technologies, providing users with an even more dynamic desktop experience and improving the administration of Flex+ in enterprise environments.

Flex+ multi-tenancy support for IT departments
Immidio Flex+ has always supported multi-tenant environments, and this release introduces much improved management of scenarios with multiple environments, such as different customers, DTAP, or separately managed organizational divisions, for instance.

Such setups can now be managed from within a single instance of the Flex+ management console, making it possible for the IT department to switch between these environments and also export configuration items from one environment to another.

An even more dynamic desktop experience
In the initial release of Flex+, Immidio introduced many capabilities for managing the user environment. Flex+ support for shortcuts, file type associations and printers is now even more powerful thanks to the new UEM Refresh feature, which during a Windows session reapplies these user environment settings, dynamically re-evaluating conditions.

Another new feature is Triggered Tasks which executes a custom or built-in task (like UEM Refresh) when a certain trigger occurs. The triggers that Flex+ supports are the lock/unlock of a workstation and disconnect/reconnect of a remote session in VDI and RDS environments.

To improve the dynamic adaption of the Windows user environment, based on role, device and location, this release extends the conditions available in Flex+. The new battery condition makes it easier to detect laptops and tablet devices. The new “Computer or User in Active Directory” condition helps determine the role of the user within the organization and the place of the currently used device within the IT infrastructure.

Support of latest technologies
Immidio Flex+ now supports personalization for Microsoft App-V 5.0, in addition to the existing App-V 4.x integration. Platform support has been extended with Windows 8 and Server 2012.

Other improvements
Many other improvements have been made to the Flex+ management console and client component. These are all documented in the Administrator’s Guide of this Flex+ release.

When configuring certificates for a lync 2010 environment, I noticed that I made a typo. Failing to correct the problem via the topology builder, I had to uninstall the lync software. After correcting my typo, the installation failed to install. This was the error I got:

After doing some digging I noticed also an event in the eventviewer
:

Opening the log file as mentioned in the event, it turned out I had something to do with an duplicate entry in the applicationhost.config.

As stated in the error it had something to do with a duplicate entry at line 421. Opening the applicationhost.config learned that line 421 didn’t had anything to do with lync. The trick was to find OCSAuthHelperModule:

<add name=”OCSAuthHelperModule” image=”C:\Windows\Assembly\GAC_64\Microsoft.Rtc.Server.WebInfrastructure\4.0.0.0__31bf3856ad364e35\Microsoft.Rtc.Server.WebInfrastructure.dll” preCondition=”integratedMode,runtimeVersionv2.0,bitness64″ />

After deleting this entry, the installation went good!

%Windir%\System32\inetsrv\config\

Special thnx to Techsps

New Features and Feature Enhancements:

• Edge Security Pack – A range of new security features has been added to the LoadMaster.
• Sub-VS Support – The LoadMaster now supports the creation and management of sub-VSs.
• Graphical Metrics – There is a new dashboard home screen with the capability to display graphical performance information.
• New License format – A new license format has been introduced
• Oracle VirtualBox VLM – A new VLM package, to support VLM installation within an Oracle VirtualBox environment is available
• MIBS files have been updated
• SID and revision information included in IPS logging
• VLAN Separation per Interface
• Support for larger TCP window sizes
• ‘Kill switch’ is now supported on all LoadMaster versions
• LM-R320 has its serial number visible on the WUI
• The Netconsole Host interface is configurable via the WUI

Issues Resolved:

• Issue with SMTP STARTTLS when a client sends an EHLO is resolved
• Issue with ACL whitelist allowing other IPs is resolved
• Issue with switching VS types under load is resolved
• Some reboot issues have been resolved
• An issue with caching on Firefox has been resolved
• The “-“ character is now allowed in the DNS Search Domain field
• Issues with the MIBS have been resolved
• A circular routing problem has been resolved
• SNMP trap Source IP has been changed to pre 5.1-48 behaviour
• SSL renegotiation can be toggled on/off
• SSLv2 is no longer used for LoadMaster initiated SSL connections
• An issue with Not Available Redirection XSS has been resolved
• The Default IP is now displayed on the WUI when DHCP fails
• An issue with VS Specific insert X-Clientside header being overwritten by system default has been resolved
• The “-“ character is now allowed in the User Login field
• An issue with the Fail on Match functionality has been resolved
• An issue with Maximum Cache Size has been resolved

Known Issues:

• Quick setup Help appears automatically if no IP address is configured on the LM if a VLAN is configured on eth0 and no IP address is assigned to the underlying interface (eth0)

LoadMaster version v7.0-4 supports the following hardware:

• LM-2000
• LM-2200
• LM-2500
• LM-2600
• LM-3500
• LM-3600
• LM-5300
• LM-5500
• LM-Exchange
• LM-R320
• VLM-100
• VLM-1000
• VLM-Exchange

NOTE – ESP is supported on select LoadMaster models and new VLM installations.

Learn more about LoadMaster 7.0:

Manual

Full Release Notes

Full Documentation

• scalability to 64 TB instead of 2040GB
• better performance by offering 4 K sector matching
• protection against data corruption during power outages

Using PowerShell to Convert to VHDX

You can dispense with the time-consuming wizard by using PowerShell. This will be extremely useful if you need to use a script to automate lots of VHD conversions across many virtual machines. The following snippet will convert a VHD to a VHDX:

Convert-VHD –Path d:\VM01\Disk0.vhd –DestinationPath d:\VM01\Disk0.vhdx

When you create a new VHDX file (not converted) it has a physical sector size of 4 K. A converted VHDX file has a physical sector size of 512 Bytes. You can change the physical sector size of a converted VHDX by running this piece of PowerShell before you power up the virtual machine:

set-vhd d:\VM01\Disk0.vhdx -PhysicalSectorSizeBytes 4096

Now you have a virtual machine that is using the best kind of virtual machine storage, the VHDX format virtual hard disk

The above instructions do not finish the job. The next essential set of steps are:

1. Open the settings of the virtual machine.
2. Replace the VHD with the VHDX.
3. Start and test the virtual machine.
4. Delete the VHD file.

And Install

KB2788525: You cannot enable external load balancing on a Windows Server 2012-based DirectAccess server.

Add or Remove Server

Run the following Windows PowerShell commands:

PS C:\> Import-Module ServerManager
PS C:\> Add-WindowsFeature -name FS-Data-Deduplication
PS C:\> Import-Module Deduplication
PS C:\> Enable-DedupVolume E: & Enable-DedupVolume D:

And wait….

Saving already 240GB on my home lab…. Dedub is great

A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API ‘”CreateCluster() failed with 0×5. Error: Access is denied”‘ failed.. [Server: ward-02.wardvissers.local]

Assigning “Full Control” to Exchange Trusted Subsystem on , I assumed should fix the issue, however, it actually produced a completely different error when I tried to add the mailbox server to DAG again:

An Active Manager operation failed with a transient error. Please retry the operation. Error: The fully qualified domain name for node ‘DAG01′ could not be found.

Solution:

Pre-stage the CNO (CLUSTER NAME OBJECT)

1. Open Active Directory Users and Computers.
2. Expand the forest node.
3. Right-click the organizational unit (OU) in which you want to create the new account, select New, and then select Computer.
4. In New Object – Computer, type the computer account name for the CNO in the Computer name box. This is the name that you’ll use for the DAG. Click OK to create the account.
5. Right-click the new computer account, and then click Disable Account. Click Yes to confirm the disable action, and then click OK.

Assign permissions to the CNO (CLUSTER NAME OBJECT)

1. Open Active Directory Users and Computers.
2. If Advanced Features aren’t enabled, turn them on by clicking View, and then clicking Advanced Features.
3. Right-click the new computer account, and then click Properties.
4. In <Computer Name> Properties, on the Security tab, click Add to add either the computer account for the first node to be added to the DAG or to add the Exchange Trusted Subsystem USG:
   • To add the Exchange Trusted Subsystem, type Exchange Trusted Subsystem in the Enter the object names to select field. Click OK to add the USG. Select the Exchange Trusted Subsystem USG and in the Permissions for Exchange Trusted Subsystem field, select Full Control in the Allow column. Click OK to save the permission settings.
   • To add the computer account for the first node to be added to the DAG, click Object Types. In the Object Types dialog box, clear the Built-in security principals, Groups, and Users check boxes. Select the Computers check box and click OK. In the Enter the object names to select field, type the name of the first Mailbox server to be added to the DAG, and then click OK. Select the first node’s computer

 Pre-Stage the Cluster Network Object for a Database Availability Group

This is the Exchange 2013 product level required for co-existence with previous versions of Exchange, being Exchange Server 2010 SP3 or Exchange Server 2007 SP3 Rollup 10.

The Exchange Team provided a description of the major changes in CU1. You will find the announcement here; Here are some of the major changes in CU1:

• Includes Address Book Policy Routing Agent (info);
• Allows group memberships to be managed by groups (again, as it was possible in Exchange 2007 but not in Exchange 2010);
• Access to Public Folders you have added as favorites via your favorites menu either in Outlook or Outlook Web App (still no regular Public Folder tree access though);
• EAC has been enhanced and now includes Unified Messaging management and migration options;
• Many probes, monitors, and responders have been updated and improved over the RTM release;
• Get-HealthReport cmdlet has been streamlined and its performance has been optimized;
• Supports the Exchange Server 2013 Management Pack for SCOM 2007 R2 and SCOM 2012 (due at a later date);
• High Availability changes

Note that CU1 includes a schema change. Like Service Packs for earlier versions of Exchange, the Cumulative Update is indeed cumulative (hence the size of 1.3 GB) and you can install it directly, i.e. no need to install RTM first. Also, once installed you can’t uninstall CU1 or any of the installed roles. The order of upgrading servers doesn’t matter, unlike with earlier Exchange versions.

Important:

Beware Full OAB Downloads After Installing 1st Exchange 2013 Server in Existing 07/10 Environment

You can download Exchange 2013 Cumulative Update 1 here.

TMG doest not support jet Exchange 2013. But with minor changes you get it working

Change in the OWA Rule

In Exchange 2013 changed the published server logoff URL to /owa/logoff.owa

You need create a Extra Rule Exchange 2013 APPS Rule

You need the ExchangeGuid

Powershell:

Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “OrganizationCapabilityClientExtensions”} | fl exchangeGUID, primarysmtpaddress
ExchangeGuid : 3eccca51-d996-49df-b6e0-302d644fdcaa

Totally:

Hardware

AMD A8 3870K 3.00GHz 4MB FM1 Box  
Asus F1A75-V PRO AMD A75, SATA600 RAID, HDMI (ESXi5.1 Works to with extra E1000 nic) 
32GB 8×4 Kingston HyperX

Converted al my VM’s with StarWind V2V Converter

It Rocks!!!

“We found an issue with Exchange 2010 coexistence. The issue actually had an easy workaround, but we made a decision; instead of burdening you with a configuration change on all of your Exchange 2010 Client Access servers, we decided to take a code change in Exchange 2013 and solve the problem so that you will not have to make any additional configuration changes. Given that the goal of CU1 is to enable coexistence with legacy versions of Exchange, we felt this was the right decision; after all, we want to ensure that your upgrade to Exchange 2013 and your coexistence period goes as smooth as possible.”

“The release date for Exchange 2013 RTM CU1 is currently planned for April 2^nd”

Configure Outlook anywhere rule on TMG

1. Open Forefront TMG
2. Click on
3. In the Action Pane under Task click
4. Give the rule a Name ill name mine “2010 OA”
5. 
6. Next –> Next
7. 
8. Internal Site Name should be your CAS server FQDN (needs to be on the cert)
9. 
10. The external name is what you use to access OA (Also needs to be on the cert)
11. 
12. Click –> Next –> Finish –> Select the Listener. (Choose the OWA listener you created before)
13. 
    This step moves the auth from the TMG server and moves it to the Exchange
14. 
15. Modify the User set to include “all users” and remove “all authenticated users”.
16. 
17. You may get the following error you can click ok and ignore it. (Do not check require users to authenticate check box on the listener or this method will not work)
18. 
19. Finish
20. Now Outlook anywhere is published using the same listener as OWA! (Albeit without pre-auth)

You must have a internal CA

Open IIS

Go to Server Certificates

Choise Create Domain Certificate

Now you can export this Certificate .

Very handy when you want to test Exchange 2013 & TMG or any other product.

All worked fine, but logging in to https://ex2013.wardvissers.nl/ecp redirected me to the old Exchange 2010 Interface.

Solution 1:

If you have this problem, you can add the Exchange Version to the URL using “?ExchClientVer=15″.

So https://ex2013.wardvissers.nl/ecp?ExchClientVer=15 will redirect you to the correct Management Interface.

Note: If the Mailbox of the Administrator account resides on the new Exchange 2013 Server this will be obsolete.

Solution 2:

Or you add an extra / add the end https://ex2013.wardvissers.nl/ecp/

The first scenarios available show you how to deploy Exchange 2013 in an organization with no previous installations of Exchange and show you how to configure a hybrid deployment between your on-premises Exchange 2013 organization and Office 365. We’re working hard on additional scenarios, such as upgrading from Exchange Server 2007 and Exchange Server 2010. These additional scenarios will be added in the coming months.

The Deployment Assistant for Exchange 2013 is supported on most major browsers and has a completely redesigned interface that’s no longer dependent on Silverlight technology. Here’s a screenshot from the Deployment Assistant after the initial set of questions were answered and the customized checklist was generated.

The Bug descripted by Microsoft:
Rapid growth in transaction logs, CPU use, and memory consumption in Exchange Server 2010 when a user syncs a mailbox by using an iOS 6.1 or 6.1.1-based device

Temp Solution:
http://exchangeserverpro.com/block-ios-61-exchange-2010?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+ExchangeServerPro+%28Exchange+Server+Pro%29

Final Solution:

Upgrade to IOS 6.1.2

You have setup a Microsoft account in Windows 8.

You have your Active Directory (AD) username and password. Your username is usually the first part of your UCSD email address (before the @ symbol). If you forgot your password, you can reset it.

You have an Exchange account in the UCSD Campus Exchange Organization.

Click the Mail tile in the Start screen to open the Mail program

Press Windows key + I on the keyboard to open Mail settings

Select Accounts

Enter your e-mail address in the Email address field

Enter your AD passsword in the Password field

Select Show more details

Enter <yourservername> in the Server address field

Enter <yourdomain> in the Domain field

Enter your AD username in the Username field

Click Connect to add the account

“Features on Demand (FoD)” is a new concept in Windows 8 that allows administrators and image builders to reduce the amount of space. .

When you install an application that’s ask for .Net Framework 3.5 that will be automatically installed. You don’t have to deploy it automatically with it…

In Windows 8, .Net Framework 3.5 is now a Feature on Demand. And to simplify the installation of common legacy versions of the .Net Framework, .Net 3.0 and 2.0 have been included in the same feature package as 3.5. That means if any of those three versions need to be installed, all the administrator needs to do is enable the single .Net Framework 3.5 feature in Windows 8.

Installation Sources

The .Net Framework 3.5 payload can be obtained from any of the following sources:

· Windows Update (WU)

· A Windows Image file (.wim) to which the payload has been added

· The \sources\sxs folder on the installation media

There are unique advantages to using each. The source can be specified for the environment using a new Group Policy setting. It can also be specified when installing .Net 3.5 manually on an individual machine or image.

The simplest scenario is one in which WU is accessible to both the machine and the user, and the machine is not configured to obtain updates from Windows Server Update Services (WSUS). In this case, when the feature is enabled, the user will be prompted for permission to download the update. If permitted, Windows will download the payload directly from Windows Update and install the feature. Done!

In more controlled environments, administrators might want to redirect such download requests to an alternate source such as a Windows Image file (.wim) to which the payload was added, or the\sources\sxs folder from the installation media. There might also be network , proxy, or security configurations that prevent users from directly accessing Windows Update. Additionally, WSUS does not currently support the payloads for Features on Demand, although it does support the subsequent patching of the features. So in environments where machines are configured to obtain updates from WSUS, administrators will need to configure the source for initial FoD installations.

To allow administrators to manage these scenarios, a new Group Policy setting was introduced in Windows 8 / Windows Server 2012: “Specify settings for optional component installation and component repair”, located under Computer Configuration\Administrative Templates\System:

This policy allows the administrator to configure the installation of Features on Demand and feature store repair operations to use only authorized locations.

When this policy is enabled, a network location (for example, a file server) can be specified for both repair of the feature store, and enabling features whose payloads were not originally added. The Alternate source file path can point to a \sources\sxs folder or a Windows image (WIM) file using the WIM: prefix. The repair WIM can be different than the initial WIM file used for installation. You can specify multiple paths by using “;” between the paths. Valid syntax is “wim:<path to wim>:<index>”. Or “<path to sxs folder>”.

Examples:

\\server\Win8Media\sources\sxs

wim:\\server\sourcewim\install.wim:3

If you select Never attempt to download payload from Windows Update, WU is not contacted during an installation or repair operation.

If you select Contact Windows Update directly to download repair content instead of Windows Server Update Services (WSUS), attempts to add features (for example, .NET Framework 3.5) or repair the feature file store use Windows Update to download files. Target computers require Internet and WU access for this option. Normal servicing operations continue to use WSUS if it has been configured as a source.

Select Behind an Edge Device
Public name voor mij is dat is: thuis.wardvissers.nl

Remote Access Review & Next

View Remote Access Review

Finish

Overview

Policy’s

Windows 8 Client

I have a Firewall/NAT router. So you need open some ports

DirectAccess works great. Every where I work I have access to my docs & email.