====== RDP wrapper ======
''[[https://github.com/asmtron/rdpwrap|rdpwrap]]'' loads the RDP DLL so you can log in from other systems.


===== Windows Product Policy Editor =====
This inspired the rdpwrap tool. [[https://forums.mydigitallife.net/threads/windows-product-policy-editor.39411/|Original post]]:

Nov 11, 2012\\ Last edited by a moderator: Apr 29, 2018

Have you ever thought about the difference between Windows Server Datacenter and Windows Starter Edition?

All windows editions are compiled from the single code base.

Some editions can have some components while others missing them.

But its not full truth. Even starter edition already has most of the components needed to convert it to ultimate edition.

Most of features of windows are controlled by the single registry key: ''HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions\ProductPolicy''

ProductPolicy is protected by kernel - if you write the value - its content remain unchanged although ''SetValue'' operation succeeds.

To overcome this protection you need to reboot in setup mode:

<file ini HKEY_LOCAL_MACHINE\SYSTEM\Setup>
SetupType=1
CmdLine="cmd.exe"
</file>

You can change the values in this mode but they will be reverted back by Software Protection service ("''sppsvc''") according to licensing templates in ''C:\windows\system32\spp''. They are signed and cannot be changed without hacking of ''sppsvc''.

I don't know what kind of operations require ''sppsvc'' running. Most ops can be done with ''sppsvc'' disabled.

If you decided to modify ''ProductPolicy'' I suggest :

  - Disable sppsvc
  - Reboot in SetupMode
  - Change needed values
  - Save your changed policy to a file
  - Reboot in normal mode

Whenever you need to reenable ''sppsvc'':

  - Do it
  - Do all you wanted to do with sppsvc enabled
  - Disable it back
  - Reboot in SetupMode
  - Reapply your changed policy from file
  - Reboot in normal mode

=== Kernel-WindowsMaxMemAllowedX64 ===
maximum memory allowed on x64 system (in MB)

=== Kernel-WindowsMaxMemAllowedX86 + Kernel-MaxPhysicalPage ===

  * maximum memory allowed on x68 system (in MB)  
  * set them both to 65536 to unlock PAE capabilities  
  * You can have up to 64G of ram on 32-bit system!

=== WSLicensingService-EnableLOBApps+WSLicensingService-LOBSideloadingActivated ===
  * Set them both to 1 to enable sideloading of metro apps even on Win8 Core Edition

=== TerminalServices-RemoteConnectionManager-45344fe7-00e6-4ac6-9f01-d01fd4ffadfb-LocalOnly ===

^ ''1'' | Do not allow remote RDP connections |

=== TerminalServices-RemoteConnectionManager-45344fe7-00e6-4ac6-9f01-d01fd4ffadfb-MaxSessions ===
Terminal services mode
^ ''0'' | logon impossible even on console |
^ ''1'' | 1 remote connection. if a user is logged on locally he will be logged out. (workstation mode. default on win 7/win 8) |
^ ''2'' | possibility of simultaneous sessions (server mode) |

(2 is default on server)

=== volmgrx-SupportRaid5 ===
^ ''1'' | Allow software raid-5 (disabled on win7/8, enabled on server) |

=== WorkstationService-DomainJoinEnabled ===
^ ''1'' | can be joined to domain. disabled on starter/home/core edition. |

Dig, try, and you will find much more!

I offer you my tool to make ''ProductPolicy'' modification process simple and effective

%%http://www.sendspace.com/file/2ap78y%%

%%https://mega.nz/#!YtognQ6D!bKNe6xctvxa29HBtNX_QjSNrRdRgXOeb54cGHy1s-Ao%%

<code>
  File: ProductPolicyEditor_1.0.3.rar
CRC-32: f770b340
   MD4: 59c4a9e6504f4e4ac32656f1d5402b9e
   MD5: ac3c58f3cddacc57e6c1fc82e280a8cc
 SHA-1: 2715ea1a7cf9a1f3e4105a302509ac7fb69200b8
</code>