When trying to test and email account on AD Audit plus the following is displayed 

Sorry, the page you requested was not found.
Please check the URL for proper spelling and capitalization. If you’re having trouble locating a destination.



Pretty silly buy but : The allowed characters are down below:0-9,a-z,A-Z_,-,.,[email protected],?,,,:,’,/,!,[,{,],},,,|,;,`,~,#,%,^,,*,(,),+,=,”,&,{InBasicLatin},”space”

GD Star Rating
GD Star Rating

Recently a customers Aruba Wireless System was denying its wireless clients access.

A look at the logs showed Authentication failure. The Authentication was set to Radius.

A look on the radius server showed the failure reason ( 6275 ) as

The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server tls 1.0

Usually this is due to Cert expiry , however this was fine : 

Looking in the System Log and I found : 

A fatal error occurred while creating an SSL server credential. The internal error state is 10013.

This is because TLS1.0 has been disabled ( HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server\Enabled = 0 ) on a Server 2012 Server

The fix is to create Dword “TlsVersion” in the below with Value c00 for TLS 1.2



Restart Extensible Authentication Protocol service when done

GD Star Rating
GD Star Rating

Recently tried to backup a single disk of a new VM , however was failing with 

“Failed to collect VM disks. Failed to get shared disk extents. Failed to get virtual disk ” per below

7/12/2021 5:09:48 PM :: Error: Failed to collect VM (ID: CCCCCCCCCCCC) information. Failed to collect VM disks. Failed to get shared disk extents. Failed to get virtual disk (path: ‘\\CCCC.local\CCCCCCCCCCC\Virtual Machines\CCCCC02\Virtual Hard Disks\CCCCCCCC02-Pagefile.vhdx’) setting data. Job failed (‘Failed to get the disk information.

Failed to open attachment ‘\\CCCC.local\CCCCCCCCCCC\Virtual Machines\CCCCC02\Virtual Hard Disks\CCCCCCCC02-Pagefile.vhdx’. Error: ‘The process cannot


The drive I was backing up wasn’t even the drive it was erroring on. I saw someone has the error here however confirmed the disk wasn’t being used elsewhere. I migrated the VM to a new host and that fixed the issue

GD Star Rating
GD Star Rating

When opening https://portal.manage.microsoft.com/

You see

You don't have any apps yet

Your company hasn’t made any apps available to you on this device.

Getting this device managed might let you access other company resources available to you, such as email and documents. Go to Devices to get started.

However when you open the Company portal app via the store if loads the apps list fine. This happens when you have multiple enrolled devices and the browser doesn’t know while one you have logged in with 


Click on Devices

Click on the grey bar

Click on your device you are using to access the Web and click Add

GD Star Rating
GD Star Rating

Upon loading the WIM file , copying the operating system and restarting it comes up with a Parse Error for the answer file

Image Deployment : Invalid unattend answer file - Software Deployment &  Patching

The best way to find the cause of this is to press Shift and F10 ( with the function key on a surface ) and open c:\Windows\Panther\unattend.xml

Viewing this I saw the OSD computer name was 16 Characters due to the Serial number being 12 Characters and our company name being 4 XXX- which made it 16 which goes over the 15 Character limit, you can trim the computer name! 


Add this to customsettings.ini



Change OSDComputerName


GD Star Rating
GD Star Rating

Recently tried to install Windows 10 on a Thinkbook 14 g2 itl and the process would fail with 13 failures

Showing the details , there was no storage driver to format and prep the drive

The driver pack thinkbook_14_g2_itl_15_g2_itl_w1064.exe had been imported into the Deployment share \ updates and the new WIM imported into PXE ….



Download both of these

Uninstall these

Install the new ADK and PE to the MDT server

Update Deployment Share and reimport into WDS

GD Star Rating
GD Star Rating

This was set ‘Primary Sound Driver’ which caused a load of surrounding noises to get picked up. I think it was using a mic on the PC.



We managed to fix the call quality issue by changing Audio settings on the 3cx App. ..




GD Star Rating
GD Star Rating
  1. Create a system repair disc (http://windows.microsoft.com/en-US/windows7/Create-a-system-repair-disc  ). You can skip this step if you have a Windows installation media. Is a good measure to reboot and verify you can start your system from this disc.
  2. Identify which disk you want to convert (usually is #0). This can be done by looking at the number in the Windows Disk Management.
  3. Download gptgen from here http://sourceforge.net/projects/gptgen  . (You could use the Windows Disk Management Tool for this too. (diskmgmt.msc)) This tool will allow you to convert your MBR disc to GPT with the data included. 
  4. ATTENTION: After this step, your computer CANNOT BOOT until the whole process is completed. DO NOT Shut Down Unless Instructed to! 

    Unzip gptgen and then run CMD with elevated privileges. (replace the 0 with the identified disk number).

    This *will* result in a BSOD shortly after and it’s to be expected:

    gptgen.exe -w \\.\physicaldrive0

  5. Boot using your Windows installation or previously generated system repair disc.
  6. Choose language and preferences, and then select Repair Your Computer -> Troubleshoot -> Advanced options -> Command Prompt
  7. We will need the disk partitioning tool. With this, we will recreate the boot partitions. Type:


  8. Identify the boot disk where Windows is located, typing:

    list disk 

     Something like this should appear:


          Disk ###  Status         Size     Free     Dyn  Gpt

          --------  -------------  -------  -------  ---  ---

        * Disk 0    Online          128 GB      0 B        *

  9. Once identified, select the disk (replace with the correct number):

    select disk 0

  10. Verify the partitions:

    list partition

  11. Something similar at the info below should appear.

           Partition ###  Type              Size     Offset

           -------------  ----------------  -------  -------

           Partition 1    Primary            350 MB  1024 KB

           Partition 2    Primary            126 GB   350 MB

  12. Delete the previous system partition:

      select partition 1

      delete partition

  13. Create the new boot partition, Microsoft reserved partition:

      create partition EFI size=100 offset=1

      format quick fs=fat32 label="System"

      assign letter=S

      create partition msr size=128 offset=103424

  14. If you list the partitions again, you should have ended up with something like this:

           Partition ###  Type              Size     Offset

           -------------  ----------------  -------  -------

           Partition 1    System             100 MB  1024 KB

           Partition 2    Reserved           128 MB   101 MB

           Partition 3    Primary            126 GB   229 MB

  15. Ensure that your Windows installation is mounted, replacing 3 with the volume number of the Windows installation (usually 1):

      list volume

      select volume 3

      assign letter=C

  16. Exit diskpart:


  17. Generate boot partition data, replacing C: with the letter of the Windows installation (usually C:):

      bcdboot c:\windows /s s: /f UEFI

  18. Cross your fingers and then restart your computer!


GD Star Rating
GD Star Rating


Windows 10 – Update 2004 – Issues with Chrome whereby you go and launch the application in windows and the browser does not open.  What does happen though is you can see the process running in task mgr.  This happens for previously deployed workstations and new machines which are run up.  You can click several times on the chrome icon before it will open a window which is reflected by the number of chrome processes running.

There are several articles out there which all talk about removing chrome, reg entries and the profile itself.  None of those make a difference the symptoms still persist.  I have almost narrowed it down to say that it has been caused by the cumulative updates applied to Win10 Build 2004.


One interesting thing I found which is off the back of an article is if you rename the exe to chrome1 it works flawlessly every time.  Change it back to Chrome and the same symptoms persist

Fix 1)

Remove 09 Cumulative update (KB4571756) this also fixes the problem.

After finding that I was able to come up with the following https://support.google.com/chrome/thread/70587649?hl=en

Fix 2)

  • Kill all instances of Chrome
  • Go to C:\Program Files (x86)\Google\Chrome\Application or C:\Program Files\Google\Chrome\Application
  • Right click chrome.exe > Properties
  • Change settings for all users
  • Set Compatibility mode to Windows 8
GD Star Rating
GD Star Rating