Category: Microsoft

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

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

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

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:

image

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

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.

image

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

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:

      Manual

      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.

      Add Extra Windows 2012 server to DirectAccess NLB Cluster

      First you install Server 2012 and you add the Remote Access Server Role.

      And Install

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

       

      Add or Remove Server

      image

      image

      image

      image

      image

      image

      image

      Server 2012 Dedub

      Start Windows PowerShell. Right-click the Windows PowerShell icon on the taskbar, and then click Run as Administrator.

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

      dedub

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

      CreateCluster failed with 0×5 adding members to DAG in Exchange 2013

      Last weekend I was building a Exchange 2013 cluster. Since everything so far was working as expected, I proceeded with creation of DAG. From EAC, creating DAG itself worked with no issues. I then went ahead and added first mailbox server to DAG. this step, however, refused to complete with error:

      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

      Exchange 2013 Cumulative Update 1

      Today the long-awaited Cumulative Update 1 for Exchange Server 2013 was released by the Exchange Team (KB2816900). This update raises Exchange 2013 version number to 15.0.620.29.

      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.

      Translate »