Add apps to startup using this path “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKey Class Route Explained = http://technet.microsoft.com/en-us/library/cc739822(v=ws.10).aspx
Add apps to startup using this path “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKey Class Route Explained = http://technet.microsoft.com/en-us/library/cc739822(v=ws.10).aspx
Original Post: Original document: http://elmaskubilay.blogspot.co.nz/2012/06/find-guid-globally-unique-identifier-of.html
From CMD or Powershell:
wmic product list (lists all programs with GUID)
wmic product get (Generates list)
wmic product get > C:\installprogs.txt (Exports the list)
Handy link to KMS overview doco
How to troubleshoot the Key Management Service (KMS)
Also worth knowing for Windows licencing – SLMGR cmd!
Force a KMS client to activate
To activate a KMS client manually using the Slmgr.vbs script
1. Log on to the KMS client computer.
2. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
3. At the command prompt, type the following, and then press Enter:
cscript \windows\system32\slmgr.vbs /ato |
The script reports activation success or failure, along with a result code.
1.1 Converting MAK clients to KMS clients
You can spot if a MAK key has been installed by running:
c:\Windows\System32\cscript slmgr.vbs -dlv
http://technet.microsoft.com/en-us/library/cc303280.aspx
By default, Windows Vista and Windows Server 2008 operating systems use KMS for activation. You can change the activation method of a KMS client to MAK and then change it back by installing the corresponding product key. Table below lists the KMS client setup keys for Windows Vista and Windows Server 2008 volume editions.
Operating System Edition | Product Key |
Windows Vista Business | YFKBB-PQJJV-G996G-VWGXY-2V3X8 |
Windows Vista Business N | HMBQG-8H2RH-C77VX-27R82-VMQBT |
Windows Vista Enterprise | VKK3X-68KWM-X2YGT-QR4M6-4BWMV |
Windows Vista Enterprise N | VTC42-BM838-43QHV-84HX6-XJXKV |
Windows Server 2008 Datacenter | 7M67G-PC374-GR742-YH8V4-TCBY3 |
Windows Server 2008 Datacenter without Hyper-V | 22XQ2-VRXRG-P8D42-K34TD-G3QQC |
Windows Server 2008 for Itanium-Based Systems | 4DWFP-JF3DJ-B7DTH-78FJB-PDRHK |
Windows Server 2008 Enterprise | YQGMW-MPWTJ-34KDK-48M3W-X4Q6V |
Windows Server 2008 Enterprise without Hyper-V | 39BXF-X8Q23-P2WWT-38T2F-G3FPG |
Windows Server 2008 Standard | TM24T-X9RMF-VWXK6-X8JC9-BFGM2 |
Windows Server 2008 Standard without Hyper-V | W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ |
Windows Web Server 2008 | WYR28-R7TFJ-3X2YQ-YCY4H-M249D |
Windows Server 2008 R2 Standard | YC6KT-GKW9T-YTKYR-T4X34-R7VHC |
Windows Server 2008 R2 Enterprise | 489J6-VHDMP-X63PK-3K798-CPX3Y |
Latest KMS Client Setup keys can be found here:
http://technet.microsoft.com/en-us/library/ff793421.aspx
To convert the MAK client back to a KMS client, choose the correct key from the above list and run the following
C:\Windows\System32>cscript slmgr.vbs -ipk <Product_Key> |
e.g. for Windows Server 2008 Enterprise
C:\Windows\System32>cscript slmgr.vbs -ipk YQGMW-MPWTJ-34KDK-48M3W-X4Q6VMicrosoft (R) Windows Script Host Version 5.7Copyright (C) Microsoft Corporation. All rights reserved. Installed product key YQGMW-MPWTJ-34KDK-48M3W-X4Q6V successfully. |
Machines not on the domain do not pick up KMS license
KMS licensing works automatically for machines on the domain, if you have a machine on a workgroup or in a DMZ, the following will register the computer with the KMS server:
C:\Windows\System32>cscript slmgr.vbs /skms KMNAME.domain.dc:1688
Outbound + return communication to TCP port 1688 is required
If the skms option is not available, you’ve likely applied a MAK key, in order to fix this, see section 5.3
When connecting to a server/pc on the domain I often get the error msg
The terminal server has exceeded the maximum number of allowed connections.
Launch a command prompt from a computer on the same domain.
quser /server: SERVERNAME
Result shows something like this:
USERNAME SESSIONNAME ID STATE IDLE TIME LOGON TIME
User01 rdp-tcp#50 1 Active 59 11/10/2012 2 35p.m.
User02 rdp-tcp#51 2 Active 1+14:14 14/10/2012 12:53 p.m.
Use the output to identify the USER ID you want to disconnect
To disconnect a user:
Logoff /server:SERVERNAME USERID
Run the Q USER command again to confirm the user is off.
Done.
Gr8 site to trace Exchange / office 365 Connectivity https://www.testexchangeconnectivity.com/
Alt try Central Ops.Net
http://centralops.net/co/
Branch Repeater VPX is licensed based on the following:
Retail licenses require a central remote license server that contains Branch Repeater VPX base and Repeater plug-in licenses (if needed).
Note: These licenses must have their host ID based on the MAC address of the remote license server. This can be found by performing the following steps:
a. Open a command prompt.
b. Go to Citrix Licensing directory, \Program Files\Citrix\Licensing\LS
c. Type the command lmutil lmhostid
d. Sample output appears in the screen shot below:
Note: A Branch Repeater VPX Express license is limited to a 512 KB send rate, 10 accelerated connections and 5 Repeater plug-in licenses.
I cant…
Spent a long time looking for answers – how to re-set the default Admin user password on our Branch Repeaters for Windwos Server 3.0.3.
Ends up all the documentation can tell you is that “ For security, the Administrator password should be changed from its default value.”
Couldn’t find this in any of the GUI in Windows. Resorted to putty into the box and still can’t change it as the admin account can’t be amended. Bugger
Ended up disabling SSH via Configuration > Tuning in the GUI. Bye bye console…
NOTE: SSH DOES need to be enabled, if it’s switched off the branch repeater is unable to see its paired repeater across site
The Citrix Branch Repeater User guide can be found here: https://support.citrix.com/article/CTX126637
Additional user guide for Windows Branch repeaters is a little more awkward to find!
The following is for a Citrix Branch Repeater 8540 accessing via my ssh client – Putty in this case.
Assuming the box has already been configured with a primary IP you can putty in to the branch repeater
Launch an SSH application (Putty)
Use the the PRIMARY – Management IP address . For the host name enet ‘ cli@ ‘ before the IP
E.g. cli@10.10.10.10
Default user name and password for a Branch Repeater (if not set) is admin/wanscaler