I am currently working with a company using Novell with XP workstations. I would like to add a Windows 2003 Small Business Server so that I can take advantage of Remote Web Workplace. Does anyone know if that would be a problem? I'm very familiar with the Windows platform and know very little about the Novell side and don't want to disturb the Novell side due to everything that they already have in place. I guess in the back of my mind the problem that I think might happen is registering on two domains.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Novell & Windows Small Business Servers Side By Side
- Thread starter mapper65
- Start date
truthfully.
you are better learning about netware rather than cx the mix.
the features you are requiring are built in to netware anyway and are a lot more powerful and most importantly not built on IIS which is to be truthful a buit of a security hole.
also the cost justification isnt really there and the password issues etc. seems silly
they will work ok side by side but it seems silly.
you are better learning about netware rather than cx the mix.
the features you are requiring are built in to netware anyway and are a lot more powerful and most importantly not built on IIS which is to be truthful a buit of a security hole.
also the cost justification isnt really there and the password issues etc. seems silly
they will work ok side by side but it seems silly.
It's a windows guy Terry, gota throw them a bone every now and then.
I wouldn't push off the Remote Web Workplace so easily, the Novell built in tools does not really have much of the same features. Novell's Virtual Office may do the email and file access, but it does not give the user a remote desktop to their company PC, nor does it have a connector to a Windows application server.
The intergration into Novell may be difficult, but not impossible. Not very familure with RWW, only looked it up to know what I was talking about in response to this thread.
As far as logging into two domains, well, you really wouldn't be logging into two domains, just one ... eDir is NOT a domain, it's a real x.500 directory, not a Lantastic domain on steroids with some x.500 hooks. The issue your really going to have is providing the users with file access through the web page, since from what I have read, RWW will only connect to Windows boxes (look up Native File Access from Novell to solve this issue). If the user takes remote control of their PC in the office, then they will use the Novell client already installed on their PC. This should not be an issue since to use the Remote Desktop the user is really just using RDP that gives them a virtual desktop that looks the same as their desktop. If you give them an app server, then you will just need to install the Novell client on the server. This will work fine since it really is just terminal services.
The real problem you will be facing is user Id and password sync. In a small enviroment, the time old manual way may work fine. Create the user ID on both systems your self, just be sure to make the user ID the same on both sides to make life easier on your users. Then you will have to sync passwords on your own. This should work fine for under 50 users. Once this company grows you will want to look into products like Identity Manager from Novell (unsure of the name for MS's equivlent). If you get to this point, you will want to involve a Novell guy since only one of two things happen in an IDM deployment. You either screw up the entire network hosing all user ID's and passwords and start to wonder if you will ever find work again, or it all works great, user ID's sync, passwords sync and life is great. There is no middle ground with IDM, and what makes the difference is someone who knows it and somoene who doesn't.
You should also let your customer know the resource impact it will have using a single server to run this RWW. Since it will be the terminal server, the IIS server, the DN server, and will be a target server for Internet worms and high school hackers.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case![[hippy]](/data/assets/smilies/hippy.gif "[hippy] [hippy]")
Senior Network Engineer
Keep IT Simple
I wouldn't push off the Remote Web Workplace so easily, the Novell built in tools does not really have much of the same features. Novell's Virtual Office may do the email and file access, but it does not give the user a remote desktop to their company PC, nor does it have a connector to a Windows application server.
The intergration into Novell may be difficult, but not impossible. Not very familure with RWW, only looked it up to know what I was talking about in response to this thread.
As far as logging into two domains, well, you really wouldn't be logging into two domains, just one ... eDir is NOT a domain, it's a real x.500 directory, not a Lantastic domain on steroids with some x.500 hooks. The issue your really going to have is providing the users with file access through the web page, since from what I have read, RWW will only connect to Windows boxes (look up Native File Access from Novell to solve this issue). If the user takes remote control of their PC in the office, then they will use the Novell client already installed on their PC. This should not be an issue since to use the Remote Desktop the user is really just using RDP that gives them a virtual desktop that looks the same as their desktop. If you give them an app server, then you will just need to install the Novell client on the server. This will work fine since it really is just terminal services.
The real problem you will be facing is user Id and password sync. In a small enviroment, the time old manual way may work fine. Create the user ID on both systems your self, just be sure to make the user ID the same on both sides to make life easier on your users. Then you will have to sync passwords on your own. This should work fine for under 50 users. Once this company grows you will want to look into products like Identity Manager from Novell (unsure of the name for MS's equivlent). If you get to this point, you will want to involve a Novell guy since only one of two things happen in an IDM deployment. You either screw up the entire network hosing all user ID's and passwords and start to wonder if you will ever find work again, or it all works great, user ID's sync, passwords sync and life is great. There is no middle ground with IDM, and what makes the difference is someone who knows it and somoene who doesn't.
You should also let your customer know the resource impact it will have using a single server to run this RWW. Since it will be the terminal server, the IIS server, the DN server, and will be a target server for Internet worms and high school hackers.
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple
- Thread starter
- #4
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question