If you find yourself with such error when you try to map a network drive in NFS;
Network Error – 53
Type ‘NET HELPMSG 53’ for more information
Please know that some tips exist to diagnose the error.
1- Make sure the NFS client is installed on the Windows 10.
2 – Make sure to use that registry fix if the mapping is on a restricted port;
UseReservedPorts := 0 (or 1) – DWORD32
3 – Make sure to use that registry fix to match the mapping GID/UID;
AnonymousGid := XXXX (usually 1001)
AnonymousUid := XXXX (usually 1001)
4 – In the linux server, make sure the /etc/exports is setting the insecure option.
NFS server has an option of working in insecure mode (Allowing higher incoming port numbers). Windows NFS client often uses higher port numbers. You can enable this option by adding an option to the share
Example: /share *(insecure,rw) ¹
As you can see it’s generic tips and of course disabling each firewall can’t hurt to diagnose 🙂
Today I will share a tip if you need to set the default file association for a bunch of computers by Group Policy.
In my example I want to make Chrome the default browser.
Someone could tell me, why I didnt used the Chrome Group Policy extension to set it by default ? I answer, because the Windows does not take it, as the file association for .htm is not changed by the Chrome GPO extension.
The first thing to do;
Change the default browser to Chrome there;
After the change we need to generate an XML’s file to know the association set;
dism /online /Export-DefaultAppAssociations:C:\apps.xml
The file content would look that way;
<?xml version=”1.0″ encoding=”UTF-8″?>
<Association Identifier=”.3gp2″ ProgId=”WMP11.AssocFile.3G2″ ApplicationName=”Windows Media Player” />
<Association Identifier=”.adt” ProgId=”WMP11.AssocFile.ADTS” ApplicationName=”Windows Media Player” />
<Association Identifier=”.adts” ProgId=”WMP11.AssocFile.ADTS” ApplicationName=”Windows Media Player” />
<Association Identifier=”.fdf” ProgId=”FoxitPhantomPDF.FDFDoc” ApplicationName=”Foxit PhantomPDF 7.0″ />
<Association Identifier=”.htm” ProgId=”ChromeHTML” ApplicationName=”Google Chrome” />
<Association Identifier=”.html” ProgId=”ChromeHTML” ApplicationName=”Google Chrome” />
<Association Identifier=”.MP2″ ProgId=”WMP11.AssocFile.MP3″ ApplicationName=”Windows Media Player” />
<Association Identifier=”.mpa” ProgId=”WMP11.AssocFile.MPEG” ApplicationName=”Windows Media Player” />
<Association Identifier=”.MPE” ProgId=”WMP11.AssocFile.MPEG” ApplicationName=”Windows Media Player” />
<Association Identifier=”.mpeg” ProgId=”WMP11.AssocFile.MPEG” ApplicationName=”Windows Media Player” />
<Association Identifier=”.mpg” ProgId=”WMP11.AssocFile.MPEG” ApplicationName=”Windows Media Player” />
<Association Identifier=”.mts” ProgId=”WMP11.AssocFile.M2TS” ApplicationName=”Windows Media Player” />
<Association Identifier=”.pdf” ProgId=”FoxitPhantomPDF.Document” ApplicationName=”Foxit PhantomPDF 7.0″ />
<Association Identifier=”.ppdf” ProgId=”FoxitPhantomPDF.PPDF” ApplicationName=”Foxit PhantomPDF 7.0″ />
<Association Identifier=”.TS” ProgId=”WMP11.AssocFile.TTS” ApplicationName=”Windows Media Player” />
<Association Identifier=”.TTS” ProgId=”WMP11.AssocFile.TTS” ApplicationName=”Windows Media Player” />
<Association Identifier=”.WPL” ProgId=”WMP11.AssocFile.WPL” ApplicationName=”Windows Media Player” />
<Association Identifier=”.xdp” ProgId=”FoxitPhantomPDF.XDPDoc” ApplicationName=”Foxit PhantomPDF 7.0″ />
<Association Identifier=”.xfdf” ProgId=”FoxitPhantomPDF.XFDFDoc” ApplicationName=”Foxit PhantomPDF 7.0″ />
<Association Identifier=”http” ProgId=”ChromeHTML” ApplicationName=”Google Chrome” />
<Association Identifier=”https” ProgId=”ChromeHTML” ApplicationName=”Google Chrome” />
After that we need to create our GPO;
It’s in Computer Configuration\Administrative Templates\Windows Components\File Explorer\Set a default associations configuration file setting
As you can see I put my file inside NETLOGON, as all computer usualy have access there.
After that your default file association should work good ! 🙂
Today I will share a tip if you need to automount some USB device inside your Windows VM.
The goal can be to auto mount some necessary devices, in my case it was to aumount USB HDD used for the backup chain.
The first step is to mount it to the VM with the ESX’s control.
When it’s mounted, you will be able to naviguate there to find the corrcet ID;
From there we have our USB ID; Check the line HardwareID
We now need to go to our ESX datastore to edit the VM .vmx’s file;
In the file VMX, we add that line;
usb.autoconnect.device0 = “0x1058:0x25e2”
As you can see we used our hardwareID to make that entry inside the VMX
Time to test after, unplug and plug the device, and it should reconnect now 🙂
Today I wanted to share a small tip that I found if you publish Work Ressource items to your computers, but you want to publish a icon into the desktop of the user.
By default RADC support only to display the item inside your Start Menu like so;
If your customers are used to the Citrix’s way to publish to the desktop. I suggest a small folder shortcut to the RADC’s ressources.
The path to use is;
%AppData%\Microsoft\Windows\Start Menu\Programs\Work Ressources (RADC)
With that path you can create a small GPO that create the icon inside the user desktop;
Today I wanted to share a small and handy tip to test any DKIM setup.
I used to generate my DKIM key(s) and my problem were that I do not control the DNS’s server which hold my public DKIM’s key pair.
As such at first when I was sending a email to a source like hotmail.com, the header was showing me that;
dkim=fail (invalid public key)
As such, now I had to dig the why, and many website offer to check the DKIM, but I was stumbled on how to do it by hand myself.
I found that nslookup was the saviour.. again.. 🙂
So the tip is to issue;
# There you type your DKIM selector for your domain;
So if your selector is DKIM_test and your domain is contoso.com;
The string will look like that;
The result would be the current key stored for the domain for that selector;
In my case the encryption key was cuted, as some DNS server limit the TXT field to 255 characters, so the field must be split to work good.
Today I wanted to share a new bug I stumble into with Windows Server 2019.
The error is showed from the Add Role Wizard;
The request to add or remove features on the specified server failed. the operation cannot be completed because the server that you specified requires a restart
It happened to me while I tried to install the WSUS’s role, and no matter how many times I restart, the error always come back.
If such happen the first thing to look for is the WSUS Configuration wizard inside the admin’s tool, as the link would be there to finish the configuration even if the error happened in Add/Remove feature.
Click to run the Wizard and click Execute after.
If it’s the same error as me, there the wizard will fail, with a link to the error log, please open the log.
In the log locate the error at the end, there we can see the error; it’s a logon error.
In the GPO console, gpedit.msc, please add the Logon as a Service right to the MSSQL account.
NT SERVICE\MSSQL$MICROSOFT##WID in Computer Configuration—>Policies—>Windows Settings—>Security Settings—>Local Policies—>User Rights Assignment
That should do the tip 🙂
ps, another workaround there
Good news from Microsoft today, Microsoft Q&A is launched and will soon replace the Technet Forum. The direct link is there.
Good new users would be able to link to their old Technet profile in Q1 of 2020 🙂
For over 10 years the MSDN and TechNet Forums played a key part in enabling our customers to unblock their business scenarios by offering a platform where technical questions could be answered by Microsoft and the community . As time progressed, and technology evolved, the needs of the community grew beyond what the existing solution could provide. We started on a journey to identify a new, robust solution which would support our need to evolve the user experience.
We’re excited to share an important milestone in the journey, introducing the preview release of Microsoft Q&A – the place to get answers to all your technical questions on Microsoft products and services.
Just wanted to share it as it’s a good news, as the old forum was starting to show it’s ages.
Thanks everyone, and happy hunt in the news forum 🙂
Today I wanted to share a small tip if you got some problems with your Windows Server 2019 OEM Activation if you have OEM media.
I used the latest Dell OEM installation media in my case. When the virtual machine booted I used to get an activation error even if my key was valid.
Running a slmgr /ato returned me that error;
Error: 0x8007041D on a computer running Microsoft windows non-core edition, run ‘slui.exe 0x2a 0x8007041D ‘ to display the error text
At that point, even if I used my OEM media, I think it’s possibly a manufacturer problem with the media kit as in each of my cases I used to had a pre-installed version of ESX, and I selected to had the OEM OS.
To pass the activation the tip I got was simple, to use these customs settings inside the VM .vmx or parameters;
smbios.addHostVendor = TRUE
SMBIOS.reflectHost = TRUE
SMBIOS.noOEMStrings = TRUE
With those setting my virtual machine activated correctly 🙂
On Microsoft Exchange you might fall into a strange bug if a time error happen between your DC and your server.
The error start by showing that error;
Event ID 5003, MSEchangeIS
Impossible d’initialiser le service de bande de d’information car les horloges de l’ordinateur client et du serveur sn déréglées. Le problème être dû à un changement d’heure sur l’ordinateur client ou le serveur, et un redémarrage peut être nécessaire. Vérifiez que votre domaine est configuré correctement et qu’il est actuellement en ligne.
That error may appear too;
EventID 3154, MSExchangeRepl
Active Manager n’a pas pu monter la base de données XXXXXXXX sur le serveur YYYYYYYY. Erreur: Une opération Active Manager a échoué avec une erreur provisoire. Recommencez l’opération. Erreur: Échec de l’action de base de données avec une erreur passagère. Erreur: Une erreur passagère s’est produite pendant une opération de base de données. Erreur: MapiExceptionNetworkError: Unable to make admin interface connection to server (hres:0x80040115, ec=-214221227)
To recover those erreurs you must do a net time command to sync the time with your active directory server.
net time \\DC-Server /set /y
After the net time don’t forget to restart the Microsoft Exchange Active Directory Topology service;
Voila, the error will be a past memory !