From the spring cleaning dept. Ever got frustrated with having a Global Authorized File list which is a mile long? Been wanting to break down your appguard and read-only blanketing security into more manageable chunks? Then this article is for you. It will show you a very slick way of organizing security authorizations using blank/empty applications as placeholders and how you can easily move security settings inbetween them. Note the moving is a PowerFuse 2010 feature.
The article contains a nice buildingblock for you to try out also.
Click here to view the RG026 article.
From the we-work-harder-so-you-don’t-have-to dept. As an administrator or integrator, you may often find yourself in the situation you need to offer certain Controlpanel applets to the users. Unfortunatly PowerFuse doesn’t (yet) offer the ability to import Control Panels as easily as it does regular applications.
To address this, I’ve created a set of buildingblocks which includes every single applet to be found in the standard Windows XP and Windows 7 control panels. On top of that there’s a set of Extras which includes some other nice control panel applets often found. Have a look at what’s inside below: (click to enlarge).
Click here to view the article and download buildingblocks.
Here’s a bit of info which may come in handy for those of you who spend a lot of time cloning machines and contemplating using Wisdom to manage the clones. As you may know, there are 3 methods in RES Wisdom for identifying the agent:
- Using the WUID option
- The MAC address of the first NIC and
- 3) a combo of the computername and domain name.
In an environment where cloning is performed, using option 1 is not recommended as it may lead you to agents disapearing from the Wisdom console. This is due to the fact that the WUID is written into the HKLM portion of the registry, hence it will be part of the image. This is why we usually recommend either using MAC address or domain+computername as the Agent identification method here
When you uninstall the Wisdom Agent, it’s a quite clean operation. However the WUID value will remain on the target machine when you uninstall it. Although this is per design, it may have some unforseen consequences if you are in the middle of building your clone template. Hence it would be nice to know what to clean out in order to forget the Wisdom agent has ever touched a machine.
The registry keys you are looking for are:
HKLM\SOFTWARE\RES\Wisdom\Preferences\WUID
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WUID\Default
If you need to clean out the Wisdom agent completely, make sure you delete both the WUID keys.
Update: August 24th 2010 – This topic has been integrated into Technote RG028.
BuildingBlocks, Technote, Workspace Manager | RESguru | 
April 9, 2010 13:08 | 
Comments (0) 
Subscribe
