marcvip

I changed users from one domain to another since the original DC crashed with no backups......now when the users log in to win2k pro they get a different profile as expected...how do I have the users have their original profile? any utilities?

you still have to go in the share permissions and change everyone readonly to full control...........win2k3 got tighter in security

oK...i FOUND THE ISSUE...read below Microsoft Knowledge Base Article - 838777 New network shared folders automatically assign Read permissions to the Everyone group in Windows Server 2003 View products that this article applies to. For additional information about the Microsoft Windows XP Service Pack 2 fix for this problem, click the following article number to view the article in the Microsoft Knowledge Base: 836023 Windows ignores the share permissions that the registry specifies after you install Windows XP S about the Microsoft Windows XP Service Pack 2 fix for this problem SYMPTOMS When you use the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\DefaultSecurity\SrvsvcDefaultShareInfo subkey to configure the default share level permissions, the subkey value is ignored. The Everyone group is given Read permissions to any new network shares. CAUSE This problem occurs because of a change that was added to Microsoft Windows Server 2003 to make the default permissions for newly created shares more restrictive than in Microsoft Windows XP. In the release version of Windows XP, when you create a new share, the default permission gives all users full access. When you create a new share in Windows Server 2003, the default permission gives everyone Read access. Because of this change, the SrvsvcDefaultShareInfo value is overwritten with Read permissions. RESOLUTION Hotfix information A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites No prerequisites are required. Restart requirement You must restart your computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name Platform ---------------------------------------------------------------------- 24-Mar-2004 16:06 6.0.3790.144 240,128 Ntshrui.dll IA-64 24-Mar-2004 16:05 6.0.3790.144 139,776 Wntshrui.dll x86 STATUS Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION For additional information about standard terminology used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base: 824684 Description of the standard terminology that is used to describe Microsoft software updates The information in this article applies to: Microsoft Windows Server 2003, Enterprise Edition Microsoft Windows Server 2003, Standard Edition Microsoft Windows Server 2003, 64-Bit Enterprise Edition Last Reviewed: 6/4/2004 (1.1) Keywords: kbnetwork kbWinServ2003SP1fix kbWinServ2003preSP1fix kbUpgrade kbSysSettings kbSecurity kbQFE kbfix kbBug KB838777 kbAudITPRO Contact Us © 2004 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility

it was all unchecked....I copied the files from another domain so maybe it is still using the old SIDS? or...I hear that win2k3 sets shares to read only by default??

There is currently 1 win2k server in the company which is also a file and print server. I created a new different win2k3 domain/forest and copied the file data from the old server, recreated the shares and users manually in AD. After repointing all win98 and win2k stations to the new domain, they can access the files on the win2k3 dc but it is in read-only....I gave everyone full control and made the admins on the win2k3 domain owner but everyone gets read-only any ideas?