Use this where you need an account on a machine to support network connections but do not want it displayed as an interactive logon option on the Welcome Screen
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList
<UserName> REG_DWORD 0
For information regarding automatic logon look here
https://technet.microsoft.com/en-us/library/cc939702.aspx
This section applies to Windows 10 and how to have a separate local admin and local user accounts and elevate using the admin account when required. At the same time the login screen does not advertise the presence of the potential accounts to login with.
Prevent accounts appearing at the logon screen:
secpol.msc
Security Settings_Local Polices_Security Options
When using local accounts on Windows 10 you may want to set
Interactive logon:Don't Display last signed-in Enabled
If the SpecialAccounts setting above is set for the Local Admin account, this causes a limitation that you will not be able to Switch User, and nor will you be able to use RunAs Administrator to run things elevated.
There is a work around though.
Search for Notepad
Open file location
Shift Right click and select Run as a different user
Enter
.\LocalAdminAccount
password
In notepad, file open and navigate to C:\Windows\System32\cmd.exe
right click RunAs Administrator
The cmd window is now running elevated as the admin.
I can't have my cake and eat it here :(
What I want is to have local user accounts selectable but not the local admin account. However I also want the option to login interactively with the local admin account if necessary.
If the Don't Display last signed-in is enabled, then the user is inconvenienced by having to enter their account name at every login.
If the Don't Display last signed-in is disabled (default), then use can select but LocalAdmin will display unless it has the SpecialAccount key, but then there is no way to choose to login with the LocalAdmin.
I will settle for Selectable with LocalAdmin set with a SpecialAccounts entry. If interactive admin logon is needed, it will need to be enabled by removing the SpecialAccounts key first.
Thursday, April 28, 2011
Wednesday, April 13, 2011
Sequencing 32bit Registry Keys on 64bit Windows 7
During sequencing 32 bit processes writing to HKLM\Software will, as usual, end up being redirected to HKLM\Software\Wow6432node. This will be reflected in the virtual registry tab and the keys will be shown under the HKLM\Software\Wow6432node. Obvious perhaps but important to remember to avoid confusion hence this post !
Windows 7 WMP 12 database with network media
Windows Media Player (WMP) 12 on Windows 7 is supposed to build a database from the files it finds at locations specified in the Music "Library". If the music library has an entry which points to a network location, then WMP 12 fails to add the items in that location to the library. You can work around this creating a local link to the the network location and then adding the local link to the library.
Add a non-indexed UNC as a library
===========================
1. Create a folder on your hard drive for shares. i.e. c:\share
2. Create another folder in the above share. i.e. c:\share\music
2. Link the Library to this folder.
3. Delete the folder.
4. Use the mklink in an elevated command prompt to make a symbolic link. Name the link the same as the folder you created above.
i.e - mklink /d c:\share\music \\server\music
5. Done. Now you have non-indexed UNC path as a library.
Add a non-indexed UNC as a library
===========================
1. Create a folder on your hard drive for shares. i.e. c:\share
2. Create another folder in the above share. i.e. c:\share\music
2. Link the Library to this folder.
3. Delete the folder.
4. Use the mklink in an elevated command prompt to make a symbolic link. Name the link the same as the folder you created above.
i.e - mklink /d c:\share\music \\server\music
5. Done. Now you have non-indexed UNC path as a library.
Thursday, March 24, 2011
MSI Package SAP GUI 7.20
Do not attempt to capture the SAP GUI 7.20 installation with Wise Smartmonitor turned on. It causes the SAP GUI installation program to hang and you will get nowhere. Capturing can be completed with Wise Smartmonitor off.
Rather than trying to capture the raw install with the GUI and patch runs, it may be easier to utilise the SAP installation server software. This gives you the ability to create a package which can install silently, with the selected features and patch levels you require. This is a much easier propect to capture and if it all goes wrong and you need to start again you won't have to face a protracted install process during capture.
Other Notes
The capture needs a fair amout of cleaning up. A lot a COM registration infomation is not exclusively associated with the appropriate components and duplicated in large generic registry components.
A couple of ini files contained non-standard entries (don't they all?) so these were tranferred to file installs rather than inifile table contructs.
Even though office is a prerequisite capturing on a clean machine is probably preferrable here rather than one with office installed.
Rather than trying to capture the raw install with the GUI and patch runs, it may be easier to utilise the SAP installation server software. This gives you the ability to create a package which can install silently, with the selected features and patch levels you require. This is a much easier propect to capture and if it all goes wrong and you need to start again you won't have to face a protracted install process during capture.
Other Notes
The capture needs a fair amout of cleaning up. A lot a COM registration infomation is not exclusively associated with the appropriate components and duplicated in large generic registry components.
A couple of ini files contained non-standard entries (don't they all?) so these were tranferred to file installs rather than inifile table contructs.
Even though office is a prerequisite capturing on a clean machine is probably preferrable here rather than one with office installed.
Wednesday, March 9, 2011
Set Registry Keys in the App-V 4.6 environment during launch
This is particularly useful if you need to have keys set in areas of the registry that are supplied primarily by a secondary, application in a Dynamic Suite Composition (DSC). A primary application is unable to apply keys via the virtual registry in this case and adding the keys at launch can solve this. An example would be an Oracle application requiring certain keys applied to Oracle Client registry locations.
These fields go between the VIRTUALENV tags.
< REGISTRY >
< REGKEY HIVE="HKLM" KEY="SOFTWARE\Test" NOREDIR="FALSE" >
Good idea to use a tool to edit the OSD so that the XML formating is correct.
An OSD editor and other tools can be obtained from http://www.loginconsultants.com
These fields go between the VIRTUALENV tags.
< REGISTRY >
< REGKEY HIVE="HKLM" KEY="SOFTWARE\Test" NOREDIR="FALSE" >
< REGVALUE REGTYPE="REG_SZ" > some_string_that_becomes_value_of_the_default_of_the_key < /REGVALUE >
< /REGKEY >
< REGISTRY >
Good idea to use a tool to edit the OSD so that the XML formating is correct.
An OSD editor and other tools can be obtained from http://www.loginconsultants.com
Spawn a prelaunch command window for troubleshooting App-Vs
Open the OSD as described earlier.
In the <DEPENDENCY> section below the <IMPLEMENTATION> section enter the following:
WAIT can be true or false depending on whether you want to launch to continue or wait for this item to complete.
<SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="TRUE">
<HREF>cmd.exe (or path to any other application)</HREF>
</SCRIPT>
< SCRIPT EVENT="SHUTDOWN" TIMING="POST" WAIT="FALSE" PROTECT="FALSE" EXTERN="TRUE" >
< SCRIPTBODY>
net use s:\\\\sgserver\\SoftGrid /DELETE
< /SCRIPTBODY >
< /SCRIPT >
TIMING can be PRE or POST of the EVENT
WAIT
PROTECT can be TRUE (inside the bubble) FALSE (outside the bubble)
http://www.tmurgent.com/OSD_Illustrated.aspx
Good scripting primer.....
http://blog.gridmetric.com/2011/10/05/osd-scripting-primer/
Also
sfttray /exe cmd.exe "<appname>"
In the <DEPENDENCY> section below the <IMPLEMENTATION> section enter the following:
WAIT can be true or false depending on whether you want to launch to continue or wait for this item to complete.
<SCRIPT TIMING="PRE" EVENT="LAUNCH" WAIT="TRUE" PROTECT="TRUE">
<HREF>cmd.exe (or path to any other application)</HREF>
</SCRIPT>
< SCRIPT EVENT="SHUTDOWN" TIMING="POST" WAIT="FALSE" PROTECT="FALSE" EXTERN="TRUE" >
< SCRIPTBODY>
net use s:\\\\sgserver\\SoftGrid /DELETE
< /SCRIPTBODY >
< /SCRIPT >
TIMING can be PRE or POST of the EVENT
WAIT
PROTECT can be TRUE (inside the bubble) FALSE (outside the bubble)
http://www.tmurgent.com/OSD_Illustrated.aspx
Good scripting primer.....
http://blog.gridmetric.com/2011/10/05/osd-scripting-primer/
Also
sfttray /exe cmd.exe "<appname>"
Editing OSDs on the fly during launch testing.
You'll often want to adjust some aspect of the OSD during testing if a prelaunch script needs tweeking for example.
To get directly to the "active" OSD for editing carry out the following:
Launch the App-V Client and locate the item in the Applications Folder.
Right click and select properties and copy the Local OSD File string value to the clipboard.
Open Notepad with admin rights.
File_Open paste in the OSD location you copied earlier.
You can now make your edits and save before testing the effects during launch by activating the shortcut.
To get directly to the "active" OSD for editing carry out the following:
Launch the App-V Client and locate the item in the Applications Folder.
Right click and select properties and copy the Local OSD File string value to the clipboard.
Open Notepad with admin rights.
File_Open paste in the OSD location you copied earlier.
You can now make your edits and save before testing the effects during launch by activating the shortcut.
Subscribe to:
Posts (Atom)