Adding Windows OEM information

1. Type regedit in RUN dialog box or Start Menu searchbox and press Enter. It’ll open Registry Editor, now go to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion

Under this key, look for a key OEMInformation. If it doesn’t exist, create it.

2. Now select OEMInformation key and in right-side pane, create following String values and set their values as shown below:

Logopath_of_OEMlogo.bmp_file
ManufacturerAny_desired_name
ModelAny_desired_name
SupportHoursAny_desired_time_amount_like_24x7
SupportPhoneAny_desired_phone_number
SupportURLAny_desired_URL

https://www.askvg.com/add-customized-strings-in-system-properties-dialog-box-of-windows-vista/

 

 

Advertisements

Windows 10 Custom Start Menu and TaskBar sequences

Various issues and errors getting this imported and .lnk/ .url shortcuts have to be in a specific place.

<LayoutModificationTemplate
xmlns=”http://schemas.microsoft.com/Start/2014/LayoutModification
xmlns:defaultlayout=”http://schemas.microsoft.com/Start/2014/FullDefaultLayout
xmlns:start=”http://schemas.microsoft.com/Start/2014/StartLayout
xmlns:taskbar=”http://schemas.microsoft.com/Start/2014/TaskbarLayout
Version=”1″>

Cannot connect to servers through VPN The username could not be found

Using the Azure Point-to-Site VPN client we could establish a connection to servers using the FQDN only anything else would fail with a Username could not be found error which the main issue was the fact it broke GPO processing as the GPO looks at the \\domain.local DFS location rather than DC by FQDN.

\\server.domain.local fine
\\server fails
\\ipaddress fails

Following website has pointed me in the right direction

https://conetrix.com/Blog/Access-Domain-Resources-When-Connected-to-VPN

When I run the command cmdkey.exe /delete /ras everything works correctly again

I did try to edit the pbk and change the UseRaSCredentials=0 but it didn’t seem to work for me.  Still have to manually run the command above once established but I can easily fire this from a custom scheduled task

 

 

 

Windows 10 VPN connections & default DNS servers

For some reason the DNS servers for the connecting VPN client do not get used and this caused problems especially as the internal AD domain suffix was split brain DNS and was getting resolved externally first.

After trying various things including registry hacks removing IPv6 etc I found out that it worked fine as long as I specified a default DNS server and used a named connection suffix.

Downside is that this is useless as I wanted to leverage DHCP wherever I may be and hard coding DNS servers would become a problem when roaming between internally and externally.

I finally found that all I had to do was change the metric on the network interface.  For both ipv4 AND ipv6 remove automatic metric and set to 100.  After this, no problems.