shamshasan

What about using the UserEnvDebugLevel key in registry to log details of a user logging in (Steps recreated below, at end)? First of all am i correct in believing that this setting would capture processes AFTER logging in only? (If above true) Is there anyway of catching the delays (via a log) when the process boots up till before it gets to the login prompt... for example when it sit's stuck on stages such as: "Applying Computer Settings", or others... Intention being that if i could get these logs and times i can just sift through it and figure out excactly what is taking too long (rather than do guess work, turn this off turn that on, etc). Any ideas out there? STEPS: 1. Start regedit and locate the following path: HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon 2. Create a new value called UserEnvDebugLevel as a REG_DWORD, and set the value to 30002 in hexadecimal format. 3: The log file can be found at: %windir%\debug\usermode\userenv.log .

I have a problem addressed by MS whitepaper: 832161 - "You experience a delay when you use your Windows XP computer to log on to a domain or to connect to a network resource" [Note: OS: XP Pro SP2] Wanted to thoroughly understand the details before i venture into exhaustive dianostics to the problem (intention being i don't have to diagnose *all* the possible causes mentioned). Appreciate everyone's help. These questions are in the context of the problem & symptoms mentioned in the paper and i'd appreciate answers within that realm too. I understand that this can be a 'cause' of delay? However, an 'error' message isn't received. What would happen here then? So that would be an misplacement. Why do we have to place them in that particular order? Ok so this causes a delay, why? What *actually* happens (so the technical part) when you order them improperly? Why/How is this a problem? What are the technicalities involved that make this a problem? What would happen if you set things up like this? Why is this a problem? How should it be set?Also, User Profiles can provide a detailed log to aid troubleshooting. To create a detailed log file for user profiles: 1. Start regedit and locate the following path: HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon 2. Create a new value called UserEnvDebugLevel as a REG_DWORD, and set the value to 30002 in hexadecimal format. The log file can be found at: %windir%\debug\usermode\userenv.log True? I hope to use this to be able to gather data on what is causing the delays at bootup. Any advice? Thanks Title Edited - Please follow new forum rules from now on -- Martin L

I had an interesting (impossible) problem that I was working on that I figure you guys could help me out with: I have a universal set of printers: O1, O2, O3,... Ox, Oy, Ozlist maintained on Server-A. [*] Subset [O1: O3] will be made available to all other MACHINES via script. [*] Anyone USER can add subset [Ox: Oz] [*] For example: User-S has: [O1, O2, O3] & [Ox] [*] User-S also has similar object not on OUR list (Server-A) Uu, for example a USB printer, so: User-S: [O1, O2, O3] & [Ox] & [uu] Now... if I destroy O3 from Server-A. I want to be able to destroy O3 from all machines too; without destroying [Ox] & [uu] off of the user's profile. But I don't have any memory on the user's profile and no memory on the server. So how do I do a comparison of sorts to figure out: - remove O3 - don't remove Ox, Uu Know any algorithm that would do/take-care-of this?

In conclusion: In the AD/GPO environment, with roaming Profile setup for users (in order of application): 1) if there's a login script that is setting printers as default in particular OUs this will ofcourse take place on machines. 2) when logging into machines (previously used by a user), in OUs that have no login scripts setting default printers, users will see the printers set as default in the past ON THAT MACHINE. 3) when logging into machines (previously NOT used by a user EVER, e.g. a RISed machine), in OUs that have no login scripts setting default printers, users will see printer set as default in last used machine - this is an ONLY ONE TIME CASE. This case only occurs once. -=-=-=-=-=-=-=-=-=-=-=-=-=-= [ FINDINGS ] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Default printer settings are saved as per machine, i.e. the user sees the printer LAST set as default ON A PARTICULAR machine and the default printer setting has no correlation to other machines except on (1) a first time login or (2) a login script setting default printers by force. Why is there a difference between logging back onto Y or X after coming from z? - There is NO difference. except if either x & y are freshly installed/RISed machines on a domain where the user has never logged in before. Were and how are these settings being stored in the user profile. - ntuser.dat file, not a granular connection of settings (not readble :-P) - currently this file is stored in the user profile (3M file) and the local user location (1M file) - the Device value in the key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows If I manually setup a printer for my office, do I see the printer from a cluster machine? - YES (covered in first email) Does it make a difference if this a printer connected locally to a printer, or a printer share or a printer setup via LPR? - no difference Some details regarding login scripts: 'KiXtart' (scripting language) has built in functions for managing printers! -=-=-=-=-=-=-=-=-=-=-=-=-=-= [ TEST-START ] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This is a detailed outline of my thorough testing procedures and findings. * COMPUTERS: - PC-O(ffice), - PC-T(est), - PC-L(ab), * OUs: - IT (sets default printer to IT.prn... through log in script), - LP, aka Local-Printer (doesn't set default printers, allows user's to do that on machines within this OU), - Lab (sets default printer to Lab.prn... through log in script), A055.prn... is the lab/Cluster printer. * Test procedure: 01) Place <PC-O> & <PC-T> in <OU-IT> // Place <PC-L> in <OU-Lab> 02) Reboot ALL PCs 03) login to PC-O - Expected? IT.prn... - default printer? --"-- - Registry? --"-- --> Logoff 04) login to PC-T - Expected? IT.prn... - default printer? --"-- - Registry? --"-- --> Logoff 05) login to PC-L - Expected? A055.prn... - default printer? --"-- - Registry? --"-- --> Logoff 06) MOVE <PC-O> & <PC-T> into <OU-LP> 07) Reboot ALL PCs [did twice... for whatever that is worth] 08) login to PC-O - Expected? A055.prn... - default printer? IT.prn... - Registry? --"-- --> Logoff 09) login to PC-T - Expected? IT.prn... (error carried forward) - default printer? IT.prn... but could be NOT because of past printer copied over // could be because set on THIS PC on last login. - Registry? --"-- --> Logoff 10) login to PC-L - Expected? A055.prn... - default printer? --"-- - Registry? --"-- --> Logoff 11) login to PC-O AGAIN - Expected? A055.prn... (expecting registry/nuser.dat settings from past get copied over into profile) - default printer? IT.prn... - Registry? --"-- --> Logoff 12) login to PC-T AGAIN - Expected? IT.prn... (error carried forward) - default printer? --"-- ... why though? highly likely not due to 'past' - Registry? --"-- --> Logoff 13) On <PC-O> set a printer not mapped via script on user profile (off of the print share though) as default. Logoff. - Set to C156 (somebody else's office, a printer pulled off of the share) - Registry settings confirmed - printed off of it too for good measure ;-) 14) login to PC-T - Expected? C156.prn... (STILL trusting logic & expecting registry/nuser.dat settings from past get copied over into profile) - default printer? IT.prn... (confirming now that default printer settings are saved on the local machine and not copied into the user profile to roam). - Registry? --"-- --> Logoff 15) login to PC-O - Expected? C156.prn... (having recognised the pattern) - default printer? C156.prn... - Registry? --"-- --> Logoff 16) login to PC-L - Expected? A055.prn... - default printer? --"-- - Registry? --"-- --> Logoff 17) login to PC-T AGAIN - Expected? IT.prn... (having recognised the pattern) - default printer? --"-- - Registry? --"-- --> Logoff 18) login to PC-O AGAIN - Expected? C156.prn... (having recognised the pattern) - default printer? --"-- - Registry? --"-- --> Logoff 19) login to PC-T AGAIN x2 - Expected? IT.prn... (having recognised the pattern) - default printer? --"-- - Registry? --"-- --> Logoff 20) RISed <PC-T>, placed into <OU-LP> 21) Logged in with Administrator account, - default printer: --> Logoff 22) Logged into PC-O // Confirm C156.prn... as default printer // Confirm PC-O in OU-LP. Logoff. 23) Login to PC-T - Expected? C156.prn... (this time it has GOT to be due to past) - default printer? C156.prn... (halle lujiah!) - Registry? --"-- --> Logoff 24) Move PC-O into OU-IT. Login to PC-O. Logoff. Login to PC-L. Log off. 25) Login to PC-T: - Expected? C156.prn... (this time it has GOT to be due to settings saved prior) - default printer? C156.prn... (halle lujiah!!) - Registry? --"-- --> Logoff -=-=-=-=-=-=-=-=-=-=-=-=-=-= [ TEST-END ] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Got good stuff on MSKB: Article 252388: How to Add a Default Printer for All New Users shoulda saw that earlier!

Ok so here's what i understand: The default printer settings are saved in the ntuser.dat file at log off and restored and log on. The ntuser.dat file is located in the %USERPROFILE% (when roaming) however i also see the ntuser.dat file locally on the machine. This is probably explained by the fact that the profile drops things locally onto the PC and at logoff/shutdown copies things back to the profile (to avoid latency). I know most of the other folders do this when roaming. (Yeah... it's me asking and me solving and me asking again... some help/comments would be appreciated) I'm trying to understand: the environment and in particular default printer settings as per the user profile and roaming. In our environment: The login script is pushed out by GPO applied to the MACHINES (not the users). it is a simple script that: maps all selected printers that we choose to make public, goes through AD and on a case by case basis, "if in OU-X set Printer-X as default" i don't understand (although i will try to explain it) why the following happens (similar to my case above, reconstructed more properly here): -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To begin: PC-Lab in OU-Lab where Printer-Lab set as default by script, PC-Office & PC-test in OU-T where Printer-T set as default by script, i've added some hidden printer (Printer-H), off of the share (off of the printer server) to my profile (user-shams). Logging into PC-Lab default printer: prn-Lab (as expected) (Prn-H is available everywhere, since it is (1) on the share, (2) on user profile) Logged back into PC-Office default printer: Prn-T (as expected) <PC-Office & PC-test moved to some other OU where there's no login script setting default printers!> <While logged into PC-Office: set Printer-H, the manually added printer, as default> Log into PC-Lab default printer: Prn-Lab (as expected) So far so good... this is expected... script is running on OU-Lab to set Prn-Lab as default. However at this point intuition tells me that when i login to PC-Office i should either: STILL see Prn-Lab as default (on PC-Office) because: ntuser.dat saves default printer as Prn-Lab off of PC-Lab --> login at PC-Office runs no script --> ntuser.dat copied off of profile & pushes Prn-Lab from past, or see Prn-H on PC-Office as default if i've completely misunderstood how ntuser.dat is working in regards the profile... point 1 was what i was going with completely. point 2 is only coz i *know* what happened. Prn-T should not show up at all now... which is what happens. (Here i first log in to the test machine which has been dormant for so long) Logging into PC-Test default printer: prn-Lab (this is what i expected... the printer, set as default, on the past machine (running a script) is set as default here because there's no script setting default printers for the user at login on this machine (now)). (now comes the monkey wrench in my entire setup) Logging into PC-Office default printer: Prn-H. granted that Prn-H set as default on this machine, once upon a time (!!!). BUT (1) i changed this on the user profile when i logged into Prn-Lab & (2) i confirmed this change when i logged into a machine that is NOT running any scripts; the printer set as default was STILL Prn-Lab. Why is it still remembering Prn-H?!?!?!? Can anyone tell me how this works? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I wonder what would happen when: a printer OFF THE SHARE is connected locally to the users' office machine (so that gets copied into their profile), a printer is connected via LPR to the users' office machine (DOES that gets copied into their profile) Please folk... lol... ask questions if you don't get what i'm asking. Thanks Shams

Testing shows that the *default printer* on a machine is depandant upon (1) machine profile + (2) user profile. I need to know where these settings are stored. Any one have any clues?

The environment: Machines are RISed, maintained by GPOs applied to (super-set) OUs in Active Directory. (running XPpro) Office machines (O1... O9) O1 == user/X's machine. O2 == some random machine user/X has never logged into (Office machines don't have log in scripts setting default printers for users) Labs (L1... L5): (in the labs we set default printers via log-in script) Printers (P1... P9) P1 to P5 == networked printers that are installed by log-in script P6 to P9 == networked printers that are NOT installed by log-in script. Are available to install and print to via LPR/IP/Hostname. Px == printer in Lx, so when users log in to the Lab L1, login script automatically sets default printer as P1. user/X has installed some shared printers on O1. Printer P9 is set as default on O1. What is happening: Currently user/X sets default printer on O1 to wherever they please. However when user/X logs into machines in L1, P1 is defaulted to. This is fine. When user/X goes to O2, not their office machine, they see printer P1 set as the default printer. EVEN THOUGH THERE IS NO LOGIN SCRIPT SETTING A DEFAULT PRINTER (and this, i'm guessing, by power of deduction, is *why* it happens) Given the case above then... if user logs back into O1, office machine, printer P1 should still be recognised as default? Testing shows that on machine O1, the past default set printer P9 is still recognised. I'm confused. Where's the default printer setting stored on XP? user or machine? Also is this supposed to be happening? Concerns:This is a problem because: a lot of paper is being wasted because users are printing at wrong location, related: professors printing exams at lab printers because set that printer when there for class IN THE PAST!!! current printer script doesn't set paper size and hence users printing leave printers hanging, and difficult to manage print queues with current login script. You all's suggestions/questions would be appreciated. Shams PS: Hope my symantics made it easier to understand the problem rather than difficult.

In our Windows XP Pro + Active Directory + netapp servers infrastructure we're facing an annoying windows security problem with shortcuts on quicklaunch. Details: Domain machines are built off of RIS GPO through Active Directory used to dish out most settings, including user settings. User profiles (and data) are stored on a net-app box: \\net-app box\user-list\some-user\ |_ MyDocuments\ | |_ WindowsOverhead\ |... |_ Desktop\ |... |_ profile\ |... |_ Application Data\ |... ... |_ Microsoft\ |... ... ... |_ Quick Launch\ |... ... ... |... |_ <empty> <---- note |... ... ... | |... ... ... |_ Internet Explorer\ |... ... ... ... |_ Quick Launch\ |... ... ... ... ... |_ <contains shortcuts> <---- note When trying to launch applications through shortcuts on the users' quick launch we get a SECURITY WARNING with details (example, below, is of an attempt to launch IE - also GIF file linked to show details.) Name: Launch Internet Explorer Browser.lnk Publisher: UNKNOWN PUBLISHER Type: Shortcut From: <netapp-box address> <OPEN> <Cancel> Highly likely it is seen from a network site and hence *considered* potentially unsafe. Is there anyway to go around this?

Are things such as rules, Outlook interface settings, and settings such as for the reading pane settings - right or bottom... part of the Outlook PST file¿ (stuff other than Address book, mail folders, notes, tasks, calendar items - stuff which i KNOW are a part of the PST file)... are these part of the PST file?! If not... where are these stored... So i've got a general plan to roam PST files (stored on a server) for users on my Domain. Policy pushed out via GPO and ADM templates. If the above file (if there is such a thing) IS seperate from a PST file... is there a settings in ADM template that can roam that? While i'm at it what about the N2K file... can that be set to a different location via ADM template? ThankS! Shams Edit: oh... and yes... i know MS doesn't support roaming PST files and they recommend using Exchange for that still... help pleaSE?!

Now i'm wondering: Machines that already have an Outlook Profile (created in the default location: C:\...\Local Settings\...\Outlook\) ... (suppose) i've moved/copied these files to the server. I have my new configuration of outlook also ready where the profiles for all users WILL point to the files on server (and new users will get the data created on first-run). ON MACHINES THAT ALREADY HAD PROFILES SETUP (default) what is the best way of CHANGING the path to the PST file (i.e. registry keys, etc...). What about using a GPO setting? What are the PROs and CONs of using the PRF file over GPO?? My thoughts (gathered from MS knowledge base): Registry changes can be made with CIW/CMW Functional areas in the PRF file include: - A section specifying actions to take, such as ... modifying existing profiles, overwriting existing profiles ... - Sections that map information specified in earlier parts of the file to registry key settings Using Group Policy (GP) to deploy Office 2003 - good choice in the following settings: - Small- or medium-sized organizations that have already deployed and configured the Active Directory® directory service. -- definately me. > $Note: This could apply for PRF as well really. Using GP would allow us to merge user details from AD (required to deploy by GPOs) PRF is made for working with Outlook (office). Help folks?!

So: Current Configuration: Currently all our users' Outlook Profiles Settings (OPS) don't have any roaming capability. Files are also unrecoverable if lost. Files are stored in a default location: C:\Documents and Settings\<user ID>\Local Settings\Application Data\Microsoft\Outlook\ New Configuration: We recently decided to move all the OPSes to the servers and open them ON there. Mapping (suggested): \\<user ID>\WindowsOverhead\appdata\Microsoft\Outlook\ We will have an automatically created/loadable OPS (through Profile Wizard) and place that in the MST for Outlook... and use that in the MSI setup. We use AD and GPO settings and hence the domain machines will be automatically updated with this new setup of Outlook automatically after a reboot. That will solve my problem for the new setup itself. Migrating (current users): (This i feel is the biggest issue) New users will automatically get the profiles created -- so that's easy. However (!) users who currently have their own profiles already setup and dandy on their machines... how will those be copied over into the new profiles and be replaced instead? I was hoping that that's what the 'Migrating User' option (in CIW) does (without having to test it.). How would a client such as Profile Maker do this? i.e. once the new image is pushed out through GPO and the user runs Outlook instead of a new profile being created one would WANT the older profile to be copied over to \\<user ID>\WindowsOverhead\appdata\Microsoft\Outlook\. Thanks for all the help!

what about the Custum Installation Wizard tool provided in Office Resource Kit tools that provide the 'migrate user settings' option (highlighted in image below)? Have you (anyone else) used that process? BTW, looking at Profile Maker... is cool... but i was wondering if i could just keep the process as simple and limited within # of tools used, # brands jumped around between... you know keep things as consistent as possible Thanks!

We have a startup with approx 20 current users, 10 more to come. We setup a network with all machines on a domain. Most of our users have been using outlook for a while. Thus they have a profile with rules and data in a PST file -- stored locally on their machine. We want to move all their outlook profiles (PST, rules, etc) to a server and get them to point to it (UNC) from their machine (using folder redirection) so that they can roam. Does anyone know any good TOOLS/METHODS to assist in migrating outlook 2003 profiles (PST, rules, etc.)? There's one in the Custum Installation Wizard (Step 9 of 24) that i haven't tried using. Is their any documentation? Thanks

creates an account? i don't want to do that... just deal with the current account. No i'm not familliar with AutoIT. Any links? tutorials? briefs? Thanks!