Today I will share a small tip if your Windows VM get an Unknown state in your ESX.
The problem can be easily fixed by first removing the machine from the inventory, without deleting the files.
After that you will have to go back into your datastore to re-add the machine back to the inventory, by right-clicking the .VMX file, and select the Add to Inventory option.
After that the state will be green 🙂
Today I wanted to share a bug I had with some Juniper SRX-100 model and newer, when with the SSG5 it was ok.
The bug appear on the terminal when they boot on a remote subnet (DHCP relay), the DHCP take time to deliever them an IP from the DHCP relay. The problem does not appear in the local subnet where the DHCP server is. The problem appear only on newer tunnel with the Juniper.
After a *lot* of research I found out that the newest JunosOS does not handle correctly custom DHCP’s option when the relay happen…
For reference all the possible option. The important’s one in my case is the 161
The terminal were getting the IP of the server where the root configuration is, where the root configuration to pre-configure the terminal with all my RDS’s option.
The problem found was the Juniper don’t handle correctly an IP into that field, like if the ftp server is named CENTRAL_FTP with the IP 192.168.1.50, then you must use the short DNS’s name, not the full FQDN.
In my case I changed the DHCP option from 192.168.1.50 to CENTRAL_FTP and maked sure the DNS option was set correctly, and voila, the DHCP’s option started to work flawlessly via my VPN tunnel with the Juniper !
Strange bug it’s, but kinda why I share it, took time to find that culprit !
Now that doc.microsoft.com is linked with github, everyone can help. Today I wanted to share a small thing I did, really a small thing, but it was really easy to do and it add visibility.
I did my first github contribution and it get commited to be visible on microsoft directly there ! 🙂 (https://docs.microsoft.com/en-us/windows/iot-core/windows-iot-core)
The github repository is there https://github.com/MicrosoftDocs/windows-iotcore-docs
The beautiful into that is that it’s easy to do.
First you setup a GitHub’s account.
After your account is created, you read the document and check where your skill can help. In my case I selected the iot subset. There I found a typo and I corrected it.
The github repository;
The next step is to contribute, in my case I edited that file;
After that you edit your file, and in the end you click to commit your change to the master branch, and voila it’s done, it just need a verification from a staff to approve the edit. As easy as that !!
The result 🙂
Hi today, my first post of 2019 😀
I will give a small tip today, if for debugging you need to select custom perfmon counter, and you always have to redo the same selection over and over again, the tip is for you.
It’s a way to simply save the perfmon selection, as such you will need to make launch manually mmc.
- Launch the Microsoft Management Console (mmc.exe)
- File -> Add/Remove Snap-ins
- Performance Monitor, Select Add, Select OK.
- Add your Counters
- File -> Save As
After that if you launch that saved applet, you will always have by default the wanted counter.
A small tip, but handy 😀
Today I will share a small tip if you are new to the XenApp 7.15 LTSR but are an old timer of the old XenApp.
Now the session limit is no longer in the ICA-RDP configuration panel, but it now use a standard GPO to set. The XenApp service listen to that settings now;
Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits
Set time limit for disconnect sessions
The old way was by that applet;
There is a small tip if you ever need to be sure the DNS entry of your server never change, or to be sure they never get scavenged.
If you open your DNS MMC, you will see static entry and dynamic entry that way;
The tip is to show the advanced feature; and after that double-click the record you want to make static, and untick the suppress option; as seen there in french;
After clicking Ok the record will now be tagged static, and will no longer change 🙂
Enjoy the small tip, thanks everyone
In some case you might want to export all ODBC configurations from one server to another’s one.
There is a small handy tip with PowerShell to achieve that goal;
Export the DNS;
Get-OdbcDsn |Export-Clixml dsn.xml
On the other machine, we import it;
Import-Clixml dsn.xml |Add-OdbcDsn
Voila, the config is now copied between the computers.