Windows 7 32bit Made to modify the service registr

Very first talk about why to write down this kind of a company. As computer use in the provider domain,Windows 7 32bit, so inevitably will inherit the domain's Group Policy configuration. 95% of the domain the laptop or computer is XP, component of Group Coverage for Windows seven system is a bit redundant and a lot of trouble. question 1, crystal clear the virtual memory strategy Clear virtual memory techniques (Distinct virtual memory pagefile) can reduce the area to some extent the spread of laptop or computer viruses. But the challenge is should you start this technique would lessen the Windows shutdown velocity (three to 5 minutes), the shutdown is quick (13 ~ 16 seconds) from the Windows seven method is just a major blow. simply modify the group policy [HKEY_LOCAL_MACHINE System CurrentControlSet Control Session Supervisor Memory Management] is set to 0x00000000 in ClearPageFileAtShutdown can. issue 2nd, the technique update technique within the domain computers via Group Coverage might be patched by WSUS update, though for your XP technique settings, but it completely destroyed the Windows seven method alone an update mechanism,Windows 7 Enterprise, make sure you refer to To solve this issue basically the registry [HKEY_LOCAL_MACHINE Software Policies Microsoft Windows WindowsUpdate] completely eliminated. answer So to solve the previously mentioned two difficulties might be accomplished by modifying the registry,Microsoft Office Professional Plus, not surprisingly,Office 2010 Pro, some consumers will say you can actually modify the domain group coverage to achieve a certain discipline is not Group Policy about the host application consumer effect, but this strategy just isn't suggested. Reg 1st to write a registry file will likely be updated to run about, but the common is also incredibly troublesome to perform so. So think of it to produce a services running within the track record, and modify the registry contents. Windows Registry Editor Version 5.00 [-HKEY_LOCAL_MACHINE Software Policies Microsoft Windows WindowsUpdate] [HKEY_LOCAL_MACHINE Program CurrentControlSet Control Session Supervisor Memory Management] Inside the class ChangeKeyValue () strategy is employed to modify the completion with the registry operation. 1 Registry.LocalMachine.DeleteSubKeyTree (updatePath); will remove the method up to date Group Policy facts, RegSetValueEx (hKey, keyName, 0,Microsoft Office Pro 2007, RegistryValueKind.DWord, keyVal, 4); will ClearPageFileAtShutdown key adjustments to 0. 1st I try to RegNotifyChangeKeyValue methods for monitoring Technique CurrentControlSet Control Session Manager Memory Management key underneath the domain group coverage is becoming modified, will probably be modified if the implementation of RegSetValueEx strategy, but it appears that way does not operate inside the services (when it'll begin the company happens to be inside a listening state). The fact is, been tested and found just on / off when ChangeKeyValue () operation could be, so that they put the code towards the following strategy. employing Method; using System.Runtime.InteropServices; employing Microsoft.Win32; namespace RegMonitor { class RegValueSet { private static UIntPtr HKEY_LOCAL_MACHINE = new UIntPtr (0x80000002u); private static UIntPtr hKey; private const int keyRights = 0xF003F; / / KEY_ALL_ACCESS (0xF003F) private const UInt32 INFINITE = 0xFFFFFFFF; private const UInt32 WAIT_FAILED = 0xFFFFFFFF; public static void ChangeKeyValue () { string clrPath = @ > string updatePath = @ > int vOpen = RegOp