Re: Linux/Apache/PHP & Windows/IIS/ColdFusion

What they've got now is completely fine - why necessarily change it? OK OK - I know many of the reasons why, but moving to another platform, you will most likely 'lose' that 'advanced authentication'. Oooooohhhh. To gain the flexibility and stability of PHP on Linux/Apache, everyone in the company will have to learn to remember their name and password. If management thinks that's too difficult for people (a distinct possibilty, especially if you have thousands of people) you'll be better off staying where you are. You could go CGI PHP on NT, which might be a compromise, but you lose the raw speed advantage PHP as an Apache module has. What about security on a machine? Last intranet I was at in a large company, just because we were logged into the network on a machine didn't give us automatic access to the intranet - people moved around too much. You still needed to present your name and password for the intranet - and everything there was NT/IIS/ASP and ColdFusion. "Joe Sheble (Wizaerd)" wrote: > Currently in-house our intranet is made up of Windows NT, IIS, and > ColdFusion. We've also settled on MS IE as our standard browser, and use > advanced authentication for logging into the intranet. This provides > employees with one click access to the intranet without having to manually > and physically login. > > We've been tossing around the idea of switching our Intranet to Linux, > Apache and PHP but we would then lose that Advanced Atuthentication > process, no? And to even complicate it even a bit more, if accessing the > intranet internally through the network (a combination of Novell and NT) > nobody should be forced to login (it being an automatic process) but if > they access the intranet externally though the internet they have to be > prompted for their normal network login information. > > Are my managers smoking crack, or do the advanced developers here think > this is do-able? And if so, where could I find more information on setting > this all up?