Active Directory Accidental Deletion – Prevention

Accidental deletions in active directory can cause havoc and unfortunately. This may have been avoided and secondly could have been fixed in less than 10 % of the actual time spent if the environment was using one of the latest features that we included in Windows 2008 R2 ( Active Directory Recycle Bin ). Most critical situations arise due to accidental human /tool interference or configuration and it is important to be able to come out of such situations within minimal down time, Accidental Deletion in Active Directory is one such situation.

Powershell Enable Protected From Accidenta lDeletion:
Get-ADobject -Filter * -SearchBase “DC=wardvissers,DC=local” | Set-adobject -ProtectedFromAccidentalDeletion $true

unknown device – ACPI/ACPI0004/CPUSCK0 ACPI/ACPI0004/CPUSCK0 on a HP Z420

Customer wanted to deploy Windows XP 32bit on a HP Z420 machine.
For this machine is a driver pack. I imported this driver in to MDT.

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

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

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

VMware released two great documents!!

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

Antivirus Best Practices for Horizon View 5.x

Immidio releases new version of Flex+ with Support of Windows 8 & Server 2012 & APP-V 5.0

Today, Immidio releases an updated version of its flagship product Flex+. With the Immidio Flex+ workspace virtualization solution, end users get a personalized and dynamic Windows desktop that adapts to their specific situation based on aspects like role, device and location.

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.

Error while installing WebComponents.msi


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\\Microsoft.Rtc.Server.WebInfrastructure.dll” preCondition=”integratedMode,runtimeVersionv2.0,bitness64″ />

After deleting this entry, the installation went good!


Special thnx to Techsps

KEMP LoadMaster v7.0-4 firmware is now available with Edge Security Pack

Kemp announced  Firmware release LoadMaster 7.0-4. Here are the details below. Watch out for more announcements on some of the features in the coming weeks.

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:


      Full Release Notes

      Full Documentation

      Convert VHD to VHDX

      VHDX is the new and default format of virtual hard disk (VDH) that is provided by Windows 8 Client Hyper-V and Windows Server 2012 Hyper-V. There are many reasons to favor VHDX files over VHD files, including:

      • 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.