Bug 699643 - "condor reuse slot" users are on log-on screen
Summary: "condor reuse slot" users are on log-on screen
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: 2.0
Hardware: x86_64
OS: Windows
medium
medium
Target Milestone: 2.0.1
: ---
Assignee: Timothy St. Clair
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On: 655860
Blocks: 723887
TreeView+ depends on / blocked
 
Reported: 2011-04-26 09:18 UTC by Martin Kudlej
Modified: 2011-09-07 16:44 UTC (History)
4 users (show)

Fixed In Version: condor-7.6.2-0.1
Doc Type: Bug Fix
Doc Text:
C: Installation of condor on a 64-bit version of Windows C: condor-reuse-slot* accounts would appear on the welcome screen F: Update UserList registry calls to write entries to the 64-bit registry. R: Slot user accounts should now be hidden on 64-bit Windows.
Clone Of: 655860
Environment:
Last Closed: 2011-09-07 16:44:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1249 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise MRG Grid 2.0 security, bug fix and enhancement update 2011-09-07 16:40:45 UTC

Description Martin Kudlej 2011-04-26 09:18:17 UTC
+++ This bug was initially created as a clone of Bug #655860 +++

Description of problem:
There are condor-reuse-slot users on log-on screen. They are not there in other Windows installations.

Version-Release number of selected component (if applicable):
Windows 2008 R2 64
condor-win-7.6.1-0.2

How reproducible:
100%

Steps to Reproduce:
1. install Condor for Windows as Administrator
2. restart OS
3. try to log in and see condor-reuse-slot* users on log-on screen
  
Actual results:
There are condor-reuse-slot* users on log-on screen.

Comment 2 Timothy St. Clair 2011-04-26 14:26:05 UTC
Is this the only supported machine which displayed this behavior?

Comment 3 Martin Kudlej 2011-04-26 14:37:46 UTC
Yes, it's only supported OS(I've got one machine per OS) which displayed this behavior.

Comment 4 Timothy St. Clair 2011-04-26 17:44:02 UTC
From my reading it appears this is an oversight by msft on some 64-bit systems, and we are doing the correct thing.  I will investigate further, but could you please verify the following:  

1.) It does not show up on Win 7 x64-bit machines
2.) Your machine is up to date with all the latest "Hot Fixes".  

FYI: Below appears to be the correct config.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList]
"condor-reuse-slot1"=dword:00000000
"condor-reuse-slot3"=dword:00000000
"condor-reuse-slot15"=dword:00000000
"condor-reuse-slot2"=dword:00000000
"condor-reuse-slot7"=dword:00000000
"condor-reuse-slot5"=dword:00000000
"condor-reuse-slot6"=dword:00000000
"condor-reuse-slot16"=dword:00000000
"condor-reuse-slot10"=dword:00000000
"condor-reuse-slot9"=dword:00000000
"condor-reuse-slot8"=dword:00000000
"condor-reuse-slot13"=dword:00000000
"condor-reuse-slot11"=dword:00000000
"condor-reuse-slot14"=dword:00000000
"condor-reuse-slot12"=dword:00000000
"condor-reuse-slot4"=dword:00000000

Comment 5 Timothy St. Clair 2011-04-26 17:53:05 UTC
The only solutions which I've seen, has been to manually edit and mirror the contents in the 64-bit registry.  Because we compile as a 32-bit app we can not directly access the 64-bit registry in a programmatic fashion.  

I will leave this open until QE response re:hot fixes, but it appears there is little we can do other then documenting this as a known issue.

Comment 6 Martin Kudlej 2011-04-27 07:05:37 UTC
I don't see it on other 64 bit OS(also not in Win 7 64). Yes, all machines are up to date with all available hot-fixes.
I've not seen it also on Windows 2008 R2 immediately after condor installation but it has appeared after some job runs.

Comment 7 Martin Kudlej 2011-04-27 14:02:34 UTC
Mirroring from "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList" to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList" helps.

Comment 8 Martin Kudlej 2011-04-27 14:03:03 UTC
But I think it should be solved especially because of Dynamic slots.

Comment 10 Martin Kudlej 2011-04-28 08:21:19 UTC
There are unwanted users on login screen also for dynamic slots.

Comment 11 Timothy St. Clair 2011-06-14 14:41:07 UTC
regarding your d-slot comment, does this occur on 32-bit machines or just 64-bit machines.  

If it is only the latter there is little we can do other then to offer insight to the user that 32-bit apps can not write to 64-bit registry and this is actually a bug in some flavors of windows.

Comment 12 Timothy St. Clair 2011-06-14 19:08:39 UTC
need to test replacing RegCreateKey->RegCreateKeyEx && w/samDesired = KEY_WOW64_64KEY.

Comment 13 Timothy St. Clair 2011-06-16 17:56:30 UTC
modification now tracking upstream and pending review. 

https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2238

For future note: limitations in reading/writing across registries appears to be a WiX issue, not a general windows issue.

Comment 14 Timothy St. Clair 2011-06-23 13:00:39 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
C: Installation of condor on a 64-bit version of Windows
C: condor-reuse-slot* accounts would appear on the welcome screen
F: Update UserList registry calls to write entries to the 64-bit registry.
R: Slot user accounts should now be hidden on 64-bit Windows.

Comment 17 Timothy St. Clair 2011-07-28 13:28:52 UTC
Note:  If you've previously installed you will need to 

1.) uninstall old version

2.) wipe the old accounts which were created under:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserList

3.) install new version

Comment 18 Martin Kudlej 2011-07-28 13:45:29 UTC
I've uninstall condor, remove keys in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Winlogon\SpecialAccounts\UserList from registers, install condor and temporary users are still on login screen.

condor-win-7.6.3-0.3
Windows 7 64bit

Have I done anything wrong?

Comment 19 Timothy St. Clair 2011-07-28 13:58:00 UTC
There should be no accounts until jobs are actually run.. 

Updated instructions:

1.) uninstall old version of condor

2.) Wipe old accounts using admin tools, then look @ registry and clean if anything remains. 

3.) Reboot (no accounts should be there)

4.) Make certain your CM is clear of any windows jobs

5.) Install new version of condor

6.) reboot

7.) Verify there are no new accounts on login, accounts should only be created when a job is run. Also check registry.

8.) Run jobs.  Check registry entries are in the 64-bit registry

9.) reboot.

10.) Check to make certain there are no accounts on the login screen.

Comment 20 Petra Svobodová 2011-08-01 15:38:57 UTC
I proceeded all the steps from comment 19. No user accounts added by condor appear on the login screen.
But the accounts created by condor stay in the system (can be displayed via the Admin tools and they are in registers) after stopping and uninstalling the condor service.

Tim, could you possibly verify that after stopping / uninstalling condor temporary accouns may remain, please?

Raising NEEDINFO for Tim.

Comment 21 Timothy St. Clair 2011-08-01 15:53:03 UTC
Correct, after stopping and uninstalling condor the slot accounts remain, but they should be hidden.  

E.g. - not visible via the logon screen.

Comment 22 Petra Svobodová 2011-08-02 10:14:35 UTC
Tim, thank you for your help.

There are no visible condor slot account on the login screen; all the accounts are hidden in the Windows system all the time.

Verified on condor-7.6.3-0.3 and all supported 64-bit Windows systems:
- Windows7-x64
- Server2003-x64
- Server2008-x64
- Server2008R2-x64

--> VERIFIED

Comment 23 errata-xmlrpc 2011-09-07 16:44:01 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-1249.html


Note You need to log in before you can comment on or make changes to this bug.