sharklasers Posted September 30, 2014 Share Posted September 30, 2014 Hi there, Currently in a Novell / Windows environment, we're soon migrating over to AD instead of using eDirectory, what are the issues that could be faced when migrating? We currently use the iPrint client which means printers need installing each time a new user logs in, which is a pain. Any input will be helpful! Link to comment Share on other sites More sharing options...
macoman Posted September 30, 2014 Share Posted September 30, 2014 Hopefully you are using Windows Server 2012 in your environment. Steps to take: 1) Powershell is your friend. Take the time to learn it, it's very powerful, and will let you do administrative tasks from the command line, as God intended. 2) Get your head around Windows permissions as early as possible.They're bass-ackwards from what you are used to, and a frequent source of confusion. Inheritance in particular is goofy. (Windows doesn't have true inheritance, it's sort of semi-inheritance.) Also, make sure you're clear on the difference between SHARE permissions and FILE permissions. This article is a bit old, but still helpful. http://www.zdnetasia.com/10-things-about-working-with-ntfs-permissions-39352670.htm 3) It's possible to migrate in stages, running a Novell network side-by-side with an AD network, and in some cases there are definite advantages to doing so. I'm not saying you need to do this, just be aware that it's an option. 4) Group Policy Preferences allows a lot of the same functionality as ZFD, very valuable. Caveat: If you have XP workstations, you've gotta install this patch (http://www.microsoft.com/download/en/details.aspx?id=3628) to make them work. You could also use Novell Identity manager to do it, it would have the advantage of keeping accounts in sync until you've completed your migration allowing for a staged migration. goretsky and fusi0n 2 Share Link to comment Share on other sites More sharing options...
sharklasers Posted September 30, 2014 Author Share Posted September 30, 2014 Thanks for that info! We already have an AD structure in place, we're just transferring everything over to Windows Server pretty. I'm just thinking of what obvious things am I missing, users will be migrated, printers will need setting up, GPOs that link to anything Novell related will need to be amended etc. Link to comment Share on other sites More sharing options...
Roger H. Veteran Posted September 30, 2014 Veteran Share Posted September 30, 2014 Moved to Server Support Let us know how it goes :) Link to comment Share on other sites More sharing options...
sc302 Veteran Posted September 30, 2014 Veteran Share Posted September 30, 2014 printui.dll can be used to add a shared printer to a computer so that regardless of who is logged into the computer they will always have the printer installed. This is built into windows and can be used in logon scripts, if you know how to script it properly. Permissions are applied like a water fall effect by default. There is no real way to hide things from domain admins without encryption (very powerful group, only put those who really need this access in this group) Link to comment Share on other sites More sharing options...
sharklasers Posted September 30, 2014 Author Share Posted September 30, 2014 We use thin clients so they run on a citrix terminal server, printers for new users always have to be installed, or when a user who has already installed a printer visits a different PC, they have to be installed again. Link to comment Share on other sites More sharing options...
pugnus Posted September 30, 2014 Share Posted September 30, 2014 if you're using eDir credentials to login to the workstation, when you move to AD everyone will get a new workstation profile. That one frustrated our desktop folks when I migrated a few years back. Link to comment Share on other sites More sharing options...
sc302 Veteran Posted September 30, 2014 Veteran Share Posted September 30, 2014 If using citrix, you can have all of the network printers installed and then train the user to switch default printer as needed. You will not need to install it every time, it can still be done with the printui.dll command and can be handled via script for those users. If you really wanted to you could also make a GPO for it. If you wanted to make something point and clicky, you can create a vb script to change the default printer to whatever so they don't have to go into the printers folder...if you are good you can do some sort of gui, if not you can make a vb script for each printer and they will have different files to click on based on the printer they want. to add a printer: rundll32 printui.dll,PrintUIEntry /ga /n"\\servername\sharename" /ga - adds the printer to the computer, no matter who is logged in this printer will always be there /gd removes the printer there are a ton of other switches vbscript to set default printer Dim WshNetwork Set WshNetwork = CreateObject("WScript.Network") WshNetwork.SetDefaultPrinter "\\servername\printer name" macoman and goretsky 2 Share Link to comment Share on other sites More sharing options...
Recommended Posts