I've noticed a number of similar questions here on this topic but not quite on the money for the issue I'm seeing.
I have Folder Redirection turned on so the profiles are on a Windows shared folder on a File and Print Server... \folders\Profiles
I want to back up the entire Profiles directory, but as Domain Admin I don't seem to have the privileges to "select all and copy" the entire directory structure.
I set up a Active Directory on a server machine with Windows Server 2012 and I'd like to create some users with limitations like Windows Steady State does in Windows XP (locally).
Seen already the Windows SteadyState Handbook (with Windows Server 2008), but I'd like to know if anyone has tried this before, the limitations are the following:
1.
Preface: About 200 users, some XP, some Vista, some Windows 7 Enterprise. Currently there is an effort underway to upgrade all users to Windows 7 Enterprise 64-bit. The backup could be implemented once all users are using Windows 7 64-bit. The DC is not under my control, but I do have the support of those who run the DC. I am the admin of my OU.
We have a Windows Server 2008 r2 Standard and a server that everybody logs into using RDP which runs Windows Server 2003. Now when people log into the RDP server, they only use an MS-Access frontend as their shell, explorer doesn't even run. However...it appears that all of their roaming profiles are needlessly being copied over to the RDP server when they log in.
Hi – I've been struggling with this for days. It seems simple but I just can't get it done.
I have a site developed in CakePHP.
Instead of backgrounding all your profiles (which indeed causes race conditions if multiple profiles use the same interface), you can background net-profiles in rc.conf:DAEMONS=(... @net-profiles ...)You'll have the benefits of a backgrounded startup, without the drawbacks of interfering profiles.
I'm trying to configure group policy for the terminal servers, and the users that will logon to it.
I created a OU in active directory called TERMINAL-SERVERS, then i moved Terminalsrv1 and terminalsrv2 to the ou.
Created a GPO linked to the OU TERMINAL-SERVERS, and made some changes to the policy to allow roaming profiles for terminal servers.
This works great, and it seems to apply the policy
Hspasta wrote:you created your wireless profiles with 'wireless-wpa-configsection' right? Are your profiles listed in /etc/conf.d/netcfg under AUTO_PROFILES?Do you have wpa_actiond installed?The wiki states that the profiles may be 'wireless-wpa' which they are (either that or by using wifi-menu). I will see if re-creating them changes anything on the ones made this way.