Volatile user

Hello, We have has a long term issue where local accounts are not removed after users logout. I have changed to Volatile user which is set for a two day time period, I have checked the local logins on some of our machines and user accounts and their respective files are not removed from the local machine.
When a user logs in again to a machine the local profile is used, which is sometimes broken (as it looks as if it has been successfully cleared) which the corrupts the profile on the netware home drive causing a domino effect. The only solution we have at the moment is to net user /delete the local user and clear the profile on the home drive.
Can anybody assist in correcting this issue.
Server: sles11.1 zenworks 11.2
Pcs: Win 7 32 bit, agent 11.2 Client 2sp2 ir2, DLU & Roaming Profiles
User home drives: mixture of nw65sp8, sles11.1 oes11
(I have posted before and commented upon other threads, now a new sp and client ir have been released I thought I would obtain the views of the forum again.)
Thanks
Breezer

Originally Posted by breezer
Hi Leroy,
We have tried everything.
What we do know is that profiles are corrupting when the are copied back from the windows 7 machine to the network. This is now happening for the majority of staff and students using windows 7, we are continually resetting profiles on the local machines and the network.
symptons
black screen, instead of normal background (machines are licensed)
groupwise not working due to registry permission issues.
login script not running so no access to directories
no delivered zen icons or bundles
user desktop icons not delivered
zoomtext not working
jaws losing its licence
not able to remote control/view machine with zenworks tools
Part of the user profile is left behind
c:\users\USERNAME\AppData\Local\Temp - .tmp files
c:\users\USERNAME\AppData\Roaming\ - various files
fix.
1. Remove user in System properties - Advanced - there are sometime 4 or 5 'unknown' users listed here, these are deleted as well.
2. net user delete /USERNAME
3. manually delete c:\user\USERNAME
4. copy fresh windows nt 6.1 ..... to their home directory.
Does anyone have any solutions as this is seriously effecting our users.
Breezer
Hi Breezer,
what is "fresh windows nt 6.1" do you generate a default Profile with the Sysprep/copyprofile method?
Ive never used Roaming Profiles but as far as i know the usual way the roaming Profile would be created based on the default profile an a machine the first time the user logs on. never heard about preloading one into the user homedir.
I was told that "login script not working" will be fixed in IR3 foer Novell Client. Login Script will not run if the Profile is guest or mandatory.
When the "black screen" profile appears is it a TEMP Profile?
ist there a remaining key under
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\SID?
Profile State of 128 = Guest
List of Profile states:
VBScript - Meaning of values under HKLM\SOFT....\ProfileList Key
I never used Romaing Profiles in the past (except testing for for small groups)
I think there are 2 seperate cases:
1. Workplace = 1 user, 1 computer, simply use local profile
2. public PCs (student labs) =
* many users per computer
* definition: any logon is a new users logon
* use mandatory/default profiles (roaming profiles to hard to manage)
regards
MArkus
p.s. google delprof.exe and delprof2.exe

Similar Messages

Word 2007 and volatile user

Guys,
I did not know where to ask. We use volatile user and I have a problem with word 2007. I can't get word to hold the settings, toolbars etc. I was able to change normal.dotx, and that's fine in regards to the page formating, but I can't make word 2007 to remember its layout. I even copied the profile to the default profile, which worked with word 2003. Please advise. Thank you.

Jakub,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Volatile User's not being removed

We have a DLU policy that has volatile user implimented. I have been
noticing that sometimes, the user doesn't get deleted and they have a
folder in C:\documents and settings\ and their username still exists in
the windows user management console, which causes problem with the user
not being able to logon later on. It says "Account created by Novell
Zenworks" in the description box besides the user name also.
What causes this and is there anyway we can fix it so that volatile user
works everytime?
We are running Netware 6.5 servers and Zenworks 6.5.

Tried uphclean ?, see TID 10096547
Cheers Dave
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/

Recent files and volatile user

Hello:
We use a volatile user with Zenworks 6.5 so the list of recent files gets wiped off once a user logs out. Is there anyway to change that? We would like to still use a volatile user accoutns, but we would also be able to keep the list of recently opened files so the user can use it after they log off. Thank You.

Jakub Gorecki,
> We use a volatile user with Zenworks 6.5 so the list of recent files gets wiped off once a user logs out. Is there anyway to change that? We would like to still use a volatile user accoutns, but we would also be able to keep the list of recently opened files so the user can use it after they log off. Thank You.
You can move the location of "recent" through the registry. Move it to the user's home directory.
http://support.microsoft.com/kb/242557
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2195

DLU Volatile Users not clearing down

Hi all.
We're having some issues (amongst many) with 11.2.1 DLU policy and it not clearing volatile users accounts down when it should. We currently have the student policy to clear down after 2 days, but this is not happening.
It's possible our many other Zen issues is having an effect, but we were getting this on Windows 7 workstations prior to 11.2.1 also.
Setup is 11.2.1 MU2 on servers, currently a mixed MU1 and MU2 agent on devices (it's still slowly rolling out).

Hi James,
verify the root cause in your environment:
are Profiles cleared completely: ProfileList entry under HKLM, ntuser.dat and complete structure under c:\user\... ?
OR are there remains of folders under c:\users\...
To my experince under WIndows 7 the problem is mostly only that folders remain from the profile - the rest is removed. The folders are empty in most cases.
If this is the case and a problem for you, you would need to create a folder deletion script.
The folder remains have 2 implications:
USers can see other usernames that logged on to this machine under c:\users\.... However not open or browse it.
NEw Profiles will be created with username.machine.001 etc. because WIndows Profile Service doesnt find an entry for the user under HKLM ProfileList but the folder c:\users\%username% is occupied so it needs to create it with .001
this may be only a cosmetical Problem depending on your environment.
another thing: Im not sure disbling the MS Client makes any sense. Since you experinced delprof2 not working without it - it may lead to problems anyway regarding profile services.
regards
Markus
Originally Posted by JR1CCB
Hi Markus.
Many thanks for your reply.
I have created a bundle using delprof2, and the problem seems to be that it relies on the Client for Microsoft Networks, which we have uninstalled (as tested by running it on a machine with the Microsoft client enabled).
So the Novell DLU policy is only deleting the users registry hive heys? That seems useless.
James

Volatile User / Sids / Permissions

Zen 3.2 / XP workstation / Policy Package with DLU enabled, manage
existing, use edirectory credentials and volatile user, roaming profiles:
Problem:
When viewing security/permissions on any files or folders created by the
user or by an application being used by the user on the local drive, they
end up with an unknown account (S-1-5-21-4226715 etc)after subsequent
logins. I assume this is due to the volatile user setting because each
time the user logs in, workstation manager actually creates a new account
and therefore new sid. I could live with this, although it's unsightly and
sloppy. But the real problem is that the user loses rights to files upon
subsequent logins. We are using the default ntfs xp security group
permissions on the drives.
We have lots of older type apps that generate temp files, etc so losing
permissions is a problem. I don't want to just set everything to run as
unsecure user unless I absolutely have to.
Anybody else have this problem? I suppose I could just remove the volatile
user setting but then I fear I'll have another set of problems to deal
with because users will end up logging in locally and have none of their
zen stuff!

Tried uphclean ?, see TID 10096547
Cheers Dave
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/

Volatile user account

Here's what happened as close as I can figure. I have a teacher who log's in daily to a workstation with novell and a local user account on the workstation. I have a user policy package for the lab users in that room, the teacher isnt in the same policy. The teacher had a sub yesterday and the sub logged into the teacher computer using the generic novell account (which incidently was the same as the local workstation account). The policy for the lab has volatile user, edir credentials, and use local workstation account checked. So when sub logged out it removed the local workstation account and all the teachers files. Teacher comes in, tries to login and cant get to local workstation. I was able to use system restore to get her settings back, but no docs, etc. Is there a way to recover these files? I dont see any salvage files on the server at all.

ddhottinger,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Volatile users and Groupwise settings

OES2, Groupwise 7.1. Win XP on the workstations.
We're starting to use a volatile user policy on a few of our computers and have run into a snag. I need to turn off Integrations under the Documents Setup in Options.
Since the policy is creating new profiles all the time, Groupwise doesn't retain this setting. I've looked at the Client settings under C1 and don't see anything that can help.
Anyone know of a network side setting for Groupwise changes?
Thanks,
Sam

SS ISAdmin wrote:
> Ok, I placed an SR on this and found that the reg key is located in
> HKCU\Software\Novell\Groupwise\Client\Library.
> There are a host of other options in the Client folder but since it is
> the Current_User segment, it'll be different for each user.
> Since this a 24 hour volatile user, and the user profiles are created
> every day, I had to find a way to make the Reg changes happen for all
> users regardless of whether they'd logged in before.
> Ended up exporting the relevant keys and making a batch file to run on
> startup for all users.
> Works so far...
>
>
I don't do volatile profiles, but can't you assign it to Default User
and have stuff be merged in?

Dynamic Local User Issue

When i look at snapins thru consoleone i can see that Zenwork 7.0.1 snapin is installaed.
I have Novell Client 4.91 SP5 and Zenwork Client 7.0.173.91015 installed on the clients running WinXP Pro SP3.
There is different of failures that happens..
Senario 1:
I install a Latitude D610 with a WinXP Pro SP3 original CD, from scratch. I only install the drivers for the LAN-card to get access to the network. I do not update windows updates etc.
I install the Novell Client 4.91 SP5, after that i install Zenwork Client 7.0.173.91015. And apply some registry settings to make the novell client to use the "tab-function" and hide advanced settings etc..
I have my eDir user "ADMIN1" with the policy package with settings to Dynamic Local User set to create a local user with name Admin, but im not using volatile user. So the local windows user Admin will be saved when logged out.
I login once with my Admin1 user, it creates the local profile Admin from Default User (with the help of Zenworks, and the policy Dynamic Local User?). I restart the computer and login again, and the local profile Admin craches and create a new one from Default User but this local user profile is namned Admin.Computername.
Ive tested this with atleast four other computers (different hardware) so it cant be a driver issue.
Ive looked thru the local logs, and i cant find anything about any problem with reading the NTUSER.DAT as could be a problem to load the local profile.
I even tested this senario when i update all windows updates etc, with two different version of the zenworks client and so on. ive been testning this for like 100 times now atleast. and same failure is happening. Ive even tested this in a virtual environment (vmware workstation).
Senari 2:
Like the problem descried above, in some cases it loss the connection or something with the zenwork server side and the zenwork client on the client computer... Since it does not attempt to use the settings from Dynamic Local User, becuase i got the windows login window, and i have to login to an already existing windows local account (with otherwords i cant login to the Admin-profile since i dont know the login information to this account since its created by zenworks / dynamic local user settings, and from the settings there you cant set a password, just the name and role of the windows accout that should be created)..
And after a while i try again, and then the settings from Dynamic Local User passes by and log into the, (let me say) Zenworks created local user profile (set by Dynamic Local User settings).
I wanna mention that all computers thats old, no reinstallation.. I can login to without problem, without any crashes of the Windows Local Profile.
Ive succeded once without any Windows Local profile crash, rebooted this computer over and over again, and no failure. If you succed twice, it seems like its fine. But then i reinstalled this computer, just like i did to make it success. But this time it failed on the second try, and got a crashed profile....
Its kinda old hardware to the server where i have my Zenworks, could that be the case? Could it be some timeouts?
The concults i use to fix some problems in our environment updated zenworks from the serverside just before christmans.. Could it be any problems with some windows patch etc?
Any help would be appreciated!
// Jokohanho

> installed on the clients running WinXP Pro SP3.
<snip>
> I restart the computer and login again, and the local
> profile Admin craches and create a new one from Default User but this
> local user profile is namned Admin.Computername.
I only know of one XP SP3 issue that could cause this, but it involves a pw
change and RP:
"When you try to log on to a Windows XP SP3-based computer by using a
roaming profile, the roaming profile cannot load."
http://support.microsoft.com/kb/958058
Regards
Rolf Lidvall
Swedish Radio (Ltd)

XP Registry and New Users

I have the following:
NetWare 6.0 sp 3
ZENworks for Desktops 3.2 sp2
XP Pro Sp2
Client 4.9 sp2
In the user policy I am using Dynamic Local User with:
Manage existing user account
Use eDirectory credentials
Volatile user
All checked.
Also using NAL
The issue:
I install an application as an administrator e.g. WordPerfect 10. WP10 is
installed local (including registry stuff) and other users have the rights
to run it. When user1 logs in and clicks on the WP10 icon in the NAL window,
NAL pushes registry stuff. Because I am asking DLU to remove the user when
they log off - when user1 logs in again it pushes the same registry stuff
down. I know XP puts registry stuff in each users' space (then ZEN removes
it when the user logs out), but is there a way of making the registry common
to all users (remember Win 98?)? I am at a school board and I might have
over 200 students logging into any given computer and don't want to make
profiles for all of them.
Thanks for any suggestions...

Thanks, but this didn't work.
Made user1 non-volitile. Logged in as user1. Launched NAL. Installed WP10.
Logged off, then back in as user1 - Registry stuff did not get reapplied (it
did before). Logged in as Admin to local machine and copied the contents of
c:\Documents and Settings\user1 to c:\documents and Settings\Default user
(including the ntuser.dat). Logged off then back on as user2, ran NAL,
clicked the WP10 shortcut and the registry stuff got pushed down.
If I search the registry for anything to do with user1 I get many hits in
HKLM pointing to c:\Documents and Settings\user1. So I gave all users all
rights to c:\Documents and Settings\user1 - didn't help.
Did I miss a step? Or are some apps, like WP, just going to be a problem?
"Rolf Lidvall" <[email protected]> wrote in message
news:g7Qbd.3443$[email protected]..
> When a new User logs in, on XP his profile will be a copy of the
> "%SYSTEMROOT%\Documents and Settings\Default User"
> -profile.
> This is a hidden folder.
> The usual way to fix your issue is to replace that profile
> with a profile that has the desired settings, then every
> new User will get the correct settings.
> Besides the folders make sure you also replace ntuser.dat,
> this /is/ the HKCU hive.
>
> Do something like:
> 1. Log in as a User that is not volatile,
> you must be able to use this profile
> for copying later
>
> 2.Run WP and any apps that save settings
> in the Users profile
>
> 3.Log out
>
> 4. Log in as Administrator
>
> 5. Copy the Users profile from step 1 over
> "%SYSTEMROOT%\Documents and Settings\Default User"
>
> Regards
> Rolf Lidvall
> Swedish Radio (Ltd)
> NSC SysOp
>
>

Systemd kiosk volatile $HOME

How may systemd populate a volatile user $HOME from persistent storage, before users can login, or before Arch logs in automatically?
The needed rsync call is trivial. I've attempted several unit/service files. I must not know something basic. The Arch OS is a charm and pure systemd. It just needs an automated rsync.
The kiosk must avoid periodic sync (a la various AUR daemons). Users can bork it. $HOME in tmpfs leaves us in control of what lands on SSD. We can tell people to reboot a borked system. We also want to minimize slow writes and maximize SSD life.
All we need is for systemd to rsync at the right stage in the boot sequence.
Thanks Arch
fstab,
tmpfs /kioskuserhome tmpfs auto,uid=4000,gid=users,rw,nosuid,exec,noatime,size=300M,nr_inodes=30K 0 0
boot setup,
rsync --archive /home/kioskuserhome/ /

Subject to correction, here's a solution. I hope it doesn't depend on timings. It works on our kiosk. Rsync is touchy about trailing slashes but works fine. We renamed kioskuserhome to ramhome. Another annoying fact is that systemd requires absolute pathnames in execution lines.
So this rigging boots a kiosk with $HOME in tmpfs and automatically logs into tty1. From there, auto-starting X is trivia.
$HOME in tmpfs is a nice speedup since apps are always reading and writing dotfiles.
# /etc/fstab
tmpfs /ramhome tmpfs auto,uid=2000,gid=users,rw,nosuid,exec,noatime,size=300M,nr_inodes=30k 0 0
# /etc/systemd/system/ramhome-setup.service (UPDATE: see corrected unit below)
[Unit]
Description=Populate RAM user files from persistent store
After=local-fs.target
[Service]
Type=oneshot
ExecStart=/usr/bin/rsync --archive /home/ramhome/ /ramhome
RemainAfterExit=no
[Install]
RequiredBy=getty.target
And following automatic login advice but tweaking After and Install, we have
# /etc/systemd/system/[email protected]
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Autologin Getty on %I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=https://wiki.archlinux.org/index.php/Automatic_login_to_virtual_console
After=systemd-user-sessions.service plymouth-quit-wait.service ramhome-setup.service
# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes
# On systems without virtual consoles, don't start any getty. (Note
# that serial gettys are covered by [email protected], not this
# unit
ConditionPathExists=/dev/tty0
[Service]
# the VT is cleared by TTYVTDisallocate
ExecStart=-/sbin/agetty --noclear -a anyone %I 38400 linux
Type=idle
Restart=always
RestartSec=0
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
KillMode=process
IgnoreSIGPIPE=no
# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE= LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE= LC_MEASUREMENT= LC_IDENTIFICATION=
# Some login implementations ignore SIGTERM, so we send SIGHUP
# instead, to ensure that login terminates cleanly.
KillSignal=SIGHUP
[Install]
WantedBy=getty.target
Then of course the obligatory commands
# systemctl daemon-reload
# systemctl enable ramhome-setup.service
# systemctl disable getty@tty1
# systemctl enable autologin@tty1
and reboot.
UPDATE. And we have been duly corrected. The revised service per systemd creator Lennart Poettering (1,2,3) follows.
# /etc/systemd/system/ramhome-setup.service
[Unit]
Description=Populate RAM user files from persistent store
Before=systemd-user-sessions.service
[Service]
Type=oneshot
ExecStart=/usr/bin/rsync --archive /home/ramhome/ /ramhome
[Install]
WantedBy=multi-user.target
Last edited by DaveCode (2013-03-05 18:11:17)

Deploying Custom Windows 7 Logon page and switch user button

I am trying to use ZCM 11 Group Policy management to do two things. 1). Turn off the Windows 7 switch user feature that exists in the start menu and at the initial logon screen, and 2). Add a policy statement graphic to the initial logon screen in Windows 7.
Feature 1 above is done by changing 'Hide entry points for 'Fast User Switching' in Computer Configuration=>Administrative Templates=>System=>Logon. But in order to get rid of the 'Switch User' button on the initial logon screen you also have to enable 'Interactive logon: Do not display last user name' in Computer Configuration=>Windows Settings=>Security Settings=>Local Policies=>Security Options and we only want this enabled for students. There are only two options for this setting - 'enabled' and 'disabled'.
Feature 2, adding a graphic to the initial logon screen, is turned on by enabling 'Always use custom logon background' in Computer Configuration=>Administrative Templates=>System=>Logon and creating a custom bmp file placed in C:\Windows\System32\oobe\info\.
Because the 'Interactive logon: Do not display last user name' setting only has enable/disable options (the default is disable) and because user associated settings overwrite workstation associations Im using two policies, one workstation and one user as inidcated below:
User GPO :
Enable 'Interactive logon: Do not display last user name' in Computer Configuration=>Windows Settings=>Security Settings=>Local Policies=>Security Options
NOTE: This allows me to differentiate between student and staff users.
Workstation GPO:
Enable 'Hide entry points for 'Fast User Switching' in Computer Configuration=>Administrative Templates=>System=>Logon
Enable 'Always use custom logon background' in Computer Configuration=>Administrative Templates=>System=>Logon
Bundle:
Deploys the bmp file to C:\Windows\System32\oobe\info\.
Unfortunately, this setup only works as intended when the user is set up with a volatile DLU policy. When the user associated DLU is non-volatile it doesnt display the graphic and it does not remove the switch user button on the main logon screen. If I logon/logoff as a non-volatile user I get the generic Windows 7 logon page with the switch user button visible, when I logon/logoff as a volatile user I get the custom graphic logon page without the switch user button. Whats even stranger is that when I go into gpedit.msc and look at the settings after I log in, theyre correct for each type of user.
Does anyone have any insight on why I might be seeing this problem?
Ive tried to be complete as possible describing the problem but if didnt describe something correctly or someone needs additional info, please let me know.
Thanks for any assistance.
Dan

Hi Dan,
are you using Novell CLient?
The Tiles on the Login Screen also depend on the Client configuration. If there is only Novell CLient active Windows cannot display other tiles or switch user.
regards
MArkus
Originally Posted by dlietz
I am trying to use ZCM 11 Group Policy management to do two things. 1). Turn off the Windows 7 switch user feature that exists in the start menu and at the initial logon screen, and 2). Add a policy statement graphic to the initial logon screen in Windows 7.
Feature 1 above is done by changing 'Hide entry points for 'Fast User Switching' in Computer Configuration=>Administrative Templates=>System=>Logon. But in order to get rid of the 'Switch User' button on the initial logon screen you also have to enable 'Interactive logon: Do not display last user name' in Computer Configuration=>Windows Settings=>Security Settings=>Local Policies=>Security Options and we only want this enabled for students. There are only two options for this setting - 'enabled' and 'disabled'.
Feature 2, adding a graphic to the initial logon screen, is turned on by enabling 'Always use custom logon background' in Computer Configuration=>Administrative Templates=>System=>Logon and creating a custom bmp file placed in C:\Windows\System32\oobe\info\.
Because the 'Interactive logon: Do not display last user name' setting only has enable/disable options (the default is disable) and because user associated settings overwrite workstation associations Im using two policies, one workstation and one user as inidcated below:
User GPO :
Enable 'Interactive logon: Do not display last user name' in Computer Configuration=>Windows Settings=>Security Settings=>Local Policies=>Security Options
NOTE: This allows me to differentiate between student and staff users.
Workstation GPO:
Enable 'Hide entry points for 'Fast User Switching' in Computer Configuration=>Administrative Templates=>System=>Logon
Enable 'Always use custom logon background' in Computer Configuration=>Administrative Templates=>System=>Logon
Bundle:
Deploys the bmp file to C:\Windows\System32\oobe\info\.
Unfortunately, this setup only works as intended when the user is set up with a volatile DLU policy. When the user associated DLU is non-volatile it doesnt display the graphic and it does not remove the switch user button on the main logon screen. If I logon/logoff as a non-volatile user I get the generic Windows 7 logon page with the switch user button visible, when I logon/logoff as a volatile user I get the custom graphic logon page without the switch user button. Whats even stranger is that when I go into gpedit.msc and look at the settings after I log in, theyre correct for each type of user.
Does anyone have any insight on why I might be seeing this problem?
Ive tried to be complete as possible describing the problem but if didnt describe something correctly or someone needs additional info, please let me know.
Thanks for any assistance.
Dan

DLU with Windows 7 x64 & Existing local user

Hi, I have a strange bug. I have a Windows 7 x64 Enterprise SP1 that I'm trying to configure a volatile user on it. I have also configured my Windows 7 to do an auto logon with a local Windows account which is "Usager". I also modified the registry to disable CASA.The auto logon work perfectly and CASA doesn't appear either. So I have configure my DLU with the "Use the credential specified below (Always volatile)", the "Use user source password and the "Manage existing user account (if any)" options. Finally, I add to the registry the "AllowDLUWithoutNovellClient" registry key under "HKEY_LOCAL_MACHINE\\SOFTWARE\\Novell\\Authenticat ion" since I dont have the Novell client install on the computer. Now each time I log off and logon again I can see that the volatile user never applies. Why does the DLU never delete the "Usager" profile? What am I missing here? We are running here 11 SP2.
Thanks in advance for the help!

Shaun, after rechecking everything I made some little progress. I'm now able to make it work but not always! I just can't find a pattern to the why it works now and not later on. Sometimes I just reboot and that's it. Other time I can reboot the computers 10 times in a row it just won't work. Is there something in the logs on the workstation that I could use to make sense here?!
Note: I'm following the guide lines in the pdf "zen11_cm_policies.pdf" on page 30 in section "3.2.3 Implementing the Dynamic Local User Policy Without the Novell Client".
Thanks again for the help!

How to restrict group of workstations

Zenworks 3.2 sp2 & WinXP Novell Client 4.9sp2
User policy for Staff/Faculty accounts gives them DLU accounts wiht the
Admininstrator's rights - the main reason is the fact that they use PCs
mainly in the offices. Volatile User Cache is set to 366 days on office PCs.
Students get Limited DLU accounts and public PCs have Workstation
Manager configured to non-volatile accounts (Cache is unchecked).
Unfortunately some faculties treat public lab PCs as their own and they
install whatever they desire on the lab PCs (why not ? since they have
all the rights, right?)
I wonder if I could somehow restrict staff/faculty access on those
workstations through policies.
TIA
Andrzej

Well, I'm afraid there is no better solution. As long as they are
"Administrators" on the public PCs they WILL mess them up. There is very
little you can do about that (such as disabling Start->Run, regedit,
setup.exe, etc.) and it will have limited effect.
Deyan
Andrzej Zalewski wrote:
> Deyan
> I thought about it, but we have too many staff memeber sharing PCs,
> besides my boss wants to have everything as general as possible, no
> manual intervention on a deployed pc, regardless office or public lab.
> Andrzej
>
> Deyan Stoykov wrote:
>
>> Andrzej,
>> Create a local account for each faculty/staff user on his/her personal
>> PC in the office, member of the Administrators group and matching
>> his/her NDS username and password. After that reconfigure the DLU
>> policy so that they will not have administrative rights. Then they
>> will be members of Administrators on their personal PCs in their
>> offices and members of Users everywhere else. This makes most sense to
>> me.
>>
>> HTH
>> Deyan
>>
>> Andrzej Zalewski wrote:
>>
>>> Zenworks 3.2 sp2 & WinXP Novell Client 4.9sp2
>>> User policy for Staff/Faculty accounts gives them DLU accounts wiht
>>> the Admininstrator's rights - the main reason is the fact that they
>>> use PCs mainly in the offices. Volatile User Cache is set to 366 days
>>> on office PCs.
>>>
>>> Students get Limited DLU accounts and public PCs have Workstation
>>> Manager configured to non-volatile accounts (Cache is unchecked).
>>>
>>> Unfortunately some faculties treat public lab PCs as their own and
>>> they install whatever they desire on the lab PCs (why not ? since
>>> they have all the rights, right?)
>>>
>>> I wonder if I could somehow restrict staff/faculty access on those
>>> workstations through policies.
>>> TIA
>>> Andrzej

Local and Roaming profiles not being created

Hello all,
I'm in need of help and I wondered if there was anyone out there with some suggestions.
The problem is that one of our sites has Netware 5 and Zfd3.2 and there are no longer any roaming profiles or local profiles being created. Volatile user is not used. Roaming profiles go to the users home directory. All file rights are fine. DLU is still working. Novell client on W2K workstations is 4.90. All other sites appear to be OK.
I suspected that the user policy was at fault and so created a test user package and associated a test user to it = same result.
I have checked from top to bottom and compared all settings to other sites and can see no difference or anything unusual. I've been working on this for 2 days now and I'm going grey and bald.
Any suggestions anyone?
I'll buy a pint for anyone with the answer - LOL.
Thanks in advance
Alan Graham
email: [email protected]

elvisgraham,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Volatile user

Similar Messages

Maybe you are looking for