> As a side item, lack of Microsoft networking services is the one item thatUnfortunatly no, it is a matter of retraining users and that would create the issue. There would need to be significant tangable benefits for the users in other areas before we could justify this.
> has so far complicated things to the point that I am unable to roll it out to
> our users. We still have to rely on NT Terminal Services and Citrix to
> provide Windows services.Isn't this a Linux problem, not a Win4Lin problem? I had an inciteful
dialog with a guy who'd converted their network services to Linux and
had all his Windows-dependent users working 100% in Win4Lin. Seemed
like a really slick way to go. I'm pretty sure he's part of this
list, maybe he could provide some advice.Cheers --- Larry
Having said that, I would love to get feedback on success (or otherwise) from sites that have migrated away from windows. In particular, any tangable benefits and issues that required work arounds. Specific areas of interest (from my perspective) would be:
- Issues concerning building from templates for new machines and methods for updating / upgrading existing installations. (ie any reduction in support costs experienced)
- Reliability
- Handling of mobile users.
- Impact on support staff including training issues.
- Impact on users including training issues.
Regards,
Chris.
