- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Re: Cannot create home folder in A/D logged on as ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2005 06:30 AM
тАО11-15-2005 06:30 AM
Cannot create home folder in A/D logged on as Administrator(Windows Server 2003)
\\Server1\Users\%username%
and I get the folloging message:
"The \\Server1\Users\%username%
home folder was not created because you do not have created access on the server. The user account has been updated with the new home folder value but you must crete the directory manually after obtaining the required access rights."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2005 07:05 AM
тАО11-15-2005 07:05 AM
Re: Cannot create home folder in A/D logged on as Administrator(Windows Server 2003)
here is a script that i use to create user shares and set permissions and ownership. it's designed to work on existing folders as well as new users. assumes username contains no spaces
'user.bat. creates user drives and set permissions
'XCACLS is a microsoft resource kit tool
'setowner is a utility from http://ntsecurity.nu/toolbox/setowner/
'replace
'
'useage: user.bat
'
if not exist d:\users\%1 mkdir d:\users\%1
pushd d:\users\%1
xcacls d:\users\%1 /T /p
for /r %%i in (*) do setowner "%%i"
for /d %%i in (*) do setowner "%%i"
setowner d:\users\%1
net share %1$=d:\users\%1 /grant:everyone,Full /unlimited /remark:"%1's I: drive"
popd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2005 10:48 PM
тАО11-16-2005 10:48 PM
Re: Cannot create home folder in A/D logged on as Administrator(Windows Server 2003)
http://support.microsoft.com/default.aspx?scid=kb;en-us;824688
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2005 08:57 AM
тАО11-17-2005 08:57 AM
Re: Cannot create home folder in A/D logged on as Administrator(Windows Server 2003)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2005 09:08 AM
тАО11-17-2005 09:08 AM
Re: Cannot create home folder in A/D logged on as Administrator(Windows Server 2003)
when migrating 700 users to new home drives, i was able to write a 10 line script to read the list of account names, generate the home directories, assign permissions and share the folders.
bear in mind that creating the home directories from the management console will not remove them when the account is removed, nor will it assure NTFS permissions, nor correct any number of other complications.
the short answer is: it's would be more effort to convince microsoft to fix it then it would save by it's functioning.