1. Type regedit in RUN dialog box or Start Menu searchbox and press Enter. It’ll open Registry Editor, now go to:
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:
Logo – path_of_OEMlogo.bmp_file
Manufacturer – Any_desired_name
Model – Any_desired_name
SupportHours – Any_desired_time_amount_like_24x7
SupportPhone – Any_desired_phone_number
SupportURL – Any_desired_URL
If ran centrally, this is useful to see who has offline file caches to servers that may be decommissioned.
To find a specific server
Get-WmiObject Win32_OfflineFilesItem -filter “itemname = ‘\\\\server'” | ft itempath
To find all file shares use
Get-WmiObject Win32_OfflineFilesItem -filter “itemtype=2” | ft itempath
This utility will scan pre and post installation or system change to get a clear idea of which registry values / file are modified to aid deployment
In the Explorer search box enter datemodified: and select an appropriate range.
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.
Following website has pointed me in the right direction
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
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.