Page 1 of 1
Welcome Screen Disabled...Access Connections the culprit?
Posted: Mon Aug 07, 2006 8:54 am
by asics
My Windows welcome screen and fast user switching have been disabled. I went to Control Panel/User Accounts and it stated it was disabled by a program I recently installed. Here's what happened...I was having a problem with my wireless connection dropping during the first few minutes of logging on. I decided to reinstall access connections. I had also upgraded the bios to 1.09 earlier in the day. After reinstalling access connections, the welcome screen and fast user switching apparently became disabled. Anyone know what happened and how to fix it?
Posted: Mon Aug 07, 2006 9:33 am
by jdhurst
I don't use fast user switching, but I do not recall that Access Connections altered that. I *do* recall from tests that Client Security disables that. I don't use Client Security, but I do use Access Connections and it appears I could switch back to fast user switching if I wished. ... JD Hurst
Posted: Mon Aug 07, 2006 12:08 pm
by asics
jd,
Don't remember being in client security at all yesterday, but checked the settings anyway, and that was it. The client security settings allowed me to enable fast user switching, and everything returned to normal. Thanks!
Posted: Mon Aug 07, 2006 12:15 pm
by asics
As long as I'm getting things fixed, one more thing...any idea why I keep dropping my connection within a few minutes of logging on? It always happens, then reconnects and works fine. Is this some kind of conflict between access connnections and windows perhaps?
Posted: Mon Aug 07, 2006 12:33 pm
by Nick Y
Try CSS7, which uses its own 'welcome' screen (if that is what you can call it!)
If it is CSS7, in your case, you can get back to the Windows welcome screen by disabling the CSS logon; go to All Programs/ ThinkVantage/ Client Security Solution. The go the Advanced menu in top left hand corner and then 'Manage Security Policies.'
BTW trying to get back to the Windows log in screen then gave me further (recoverable) problems, so I had to stick with CSS and wait for CSS8 or 9...