W
W
WolanD912012-07-24 07:43:45
Microsoft
WolanD91, 2012-07-24 07:43:45

why doesn't Active Directory create a "desktop" folder in the user profile, the shopping cart does not work?

Good day!

There is a server on Windows Server 2008 Standart, and a client machine running Windows XP Professional SP3 + all the proposed updates.

The essence of the problem is that after entering the client machine into the domain, synchronized folders should appear in the user profile (accordingly, My Documents, Desktop...). So those folders don't exist. But the most important thing is that in folders that are synchronized with the server via AD, files are permanently deleted, bypassing the trash.

For example, I delete a file from the root of drive C - it goes to the trash. But the file deleted from the desktop is deleted permanently.

Answer the question

In order to leave comments, you need to log in

6 answer(s)
A
atreen, 2012-07-24
@WolanD91

There is no such thing by default. It's worth watching what happens in your GPO. This is evidenced by the deletion without the trash.
Maybe you have different GPOs for different lists of PCs, by default, a newly connected PC falls into one AD container, while I store all the machines in another.
Perhaps the fact that the profile is roaming somehow affects (you did not specify this, but suddenly).
I summarize, it is worth making a separate OU without policies, and on ready-made cars, look at the output of gpresult - it will show the applied policies.

M
mxc, 2012-07-25
@mxc

What kind of garbage I've been reading since morning ... Shkolohabr in my repertoire.

S
ShadowHacker, 2012-07-24
@ShadowHacker

Windows or...

F
fenst, 2012-07-24
@fenst

It seems that once I “cured” this by creating the “desktop” and “my documents” folders manually. But, of course, this is just a crutch
PS standarD

N
Nikolai Turnaviotov, 2012-07-24
@foxmuldercp

Sorry, but it was already said above that AD has nothing to do with the user profile without changing the policies on the OU - while the policies associated with profile redirection are not applied to the organizational unit in which the user and / or PC is located - AD does not at what.
Check carefully the policies that are applied to the OU with the user, the access rights to the network share in which the profiles are created - I once had hemorrhoids - the profile did not switch to the network until very strict access rights were set to \\fileserver\profiles, where the user profiles in the test OU should have been stored.
Update policies and look at gpresult output, client system logs

W
WolanD91, 2012-07-26
@WolanD91

Thanks for the help to everyone who responded

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question