Netware 6 file server migrate to Windows 2003 server
We have a Novell eDirectory with file, print.....GroupWise... Zen
works the whole shebang it works wonderfully. We just no longer have
the resources to support this. We also have an Active Directory tied
to eDirectory through Novell IDM. We want to migrate our file server
and print severs over to windows. We need to keep our current rights
to files and folders. I don't believe I can use Quest or MSDSS
services as we already have a working Active Directory and user's
already exist in it with Microsoft file and group associations.
How do I go about moving my Netware files and folders from Netware 6
to windows 2003 and maintain rights?
.
Relevant Pages
- Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
... Authentication" story and can relate to them all. ... the introduction of Active Directory. ... All rights ... > | Vincent Polite ...
(microsoft.public.inetserver.iis.security) - Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
... Authentication" story and can relate to them all. ... the introduction of Active Directory. ... All rights ... > | Vincent Polite ...
(microsoft.public.inetserver.iis.security) - Re: ADAM Synchronizer Beta - question
... This posting is provided "AS IS" with no warranties, and confers no rights. ... >> Right is not granted to the account that is used to connect to AD. ... >> Dmitri Gavrilov ... >> SDE, Active Directory Core ...
(microsoft.public.windows.server.active_directory) - Re: Error 4913: SMS cannot create the object in AD
... Does the service account have all rights to all child objects? ... Active Directory Schema Modification and Publishing for Systems Management ... Check out the SMS Technical FAQ: ... This posting is provided AS IS with no warranties and confers no rights. ...
(microsoft.public.sms.admin) - Re: Moving DCs From Default OU ?
... You cannot protect against this in any way you dream up because it just cannot be done with Active Directory. ... You might as well make them Domain and Enterprise Admins, at least you will be honest with yourself them on what rights they have. ... Again, I don't care who told you otherwise, you cannot protect the AD from someone you give admin level rights or in fact even server operator rights or even less. ... In almost every case it the thought to do this is based on some misunderstanding on how Domain Security works or some stupid plan to have a pretty hierarchy. ...
(microsoft.public.windows.server.active_directory) |
|
