It's used in Albion, WI. Redhat on older Gateway hardware. It sits right along side of the Win95 and Mac boxen. I'm pretty sure they're going to be installing it on the rest of the x86 boxen.
Have you read the Cournty Love commentary? Basically, when a band gets signed, they end up in debt for around 2 million to the label. The CD sells 500,000 copies. THe band gets shit, the label profits something like 6.6 million. Your analogy is not even close. The only way bands make money is touring, t-shirts, and shit like that. I'm a musician. That DOES NOT mean I like to take it up the ass from major labels. All I really want to do is write music, perform it, and make a damn living doing it. Porbably one of the hardest careers a person could choose. I ended up being a sysadmin simply because I want to live like a human being, not like some depraved gypsy on a tour bus forever.
Does anyone have good info about setting up one of these? Yes, I'll go an look around on Google, I want/. info first. I mean, it's not just getting an 802.11b transciever and proclaiming to the world "Here I am!". You need a way to control users access, billing stuff, how do you put it on their end? Do you sell them the transciever, rent it, make them buy there own? How do you decide where you wanna go first?
I'm assuming rural here, since most urban places have broadband available. How about selling to businesses? If you can't tell, I'm pretty interested in doing this.
First off, before the trolls get to it, no, *BSD IS NOT DYING. Ok, I'm donme with that part.
I've been using FreeBSD since early 1994 and have grown up with ti, so to speak. Even back then, I tried Linux and ended up learning FreeBSD. I'm really glad to see people writing for newbies.
Looks like I might be able to sneak PHP in here now. I've been using it for my own web development projects for a few years now and all I can say is, it kicks ass. Congrats to the PHP crew!
If you're trying to decide which direction to go in web development, take a real close look at PHP. It totally smokes.asp and can do virtually anything you can do with java, except for client side stuff like applets. It's extremely fast and pretty straight forward to learn. Can you tell I like it?
The following is the result of research into various OS and office suites. THIS IS NOT MY OPINION! It's the opinion of a commitee I work with. I deleted the agencies name to protect my ass. This is what we deal with if we want to try and convert the Gov to an OSS solution.
Technical Evaluation of Alternatives for Upgrading and Migrating the 's Desktop Operating System and Office Suite and Network Server Operating System
The Issues: Since the deployment of Windows NT approximately 6 years ago and Office 97 approximately 3 years ago, Microsoft has released two new versions of the desktop operating system and the office suite. It is anticipated that Microsoft will terminate support for our existing environment in the near future. It has also been announced that our desktop hardware vendor will discontinue support for Windows NT on laptops beginning in June of 2002 and for desktops most likely by June of 2002. It is expected that other vendors will follow suit, after Microsoft makes its announcement. Vendor support of our tools is an important part of being able to maintain our environment in its best form. It allows us to resolve issues more quickly, and when there isn't a ready solution, it is a means by which we can get the vendor to assist us in resolving our issues.
We face a similar issue for the current version of our network operating system, which is Windows NT Server. There currently is one newer version of this operating system on the market, which is called Windows 2000 Server and technically there are three flavors of this product. Microsoft has announced that it is currently beta testing another version called Windows.NET Server. We can anticipate similar desupport notices and issues for Windows NT Server in the next six months to one year.
In addition to the normal cycle of product upgrades and desupport notices, we will be faced with making licensing choices in how we choose to license Microsoft products in the future. The focus of this paper is on the technical aspects of these announcements and their impacts. Issues of licensing and funding are items, which are to be explored by , however this team is acutely aware of the current fiscal situation facing this agency and has made recommendations with this situation in mind.
The Scope of This Document: The purpose of this document is to outline the technical criteria on which decisions for migration to a new version of the desktop operating system, desktop office suite, and network operating system can be made. In addition, this document will provide a recommendation on what BEITA believes is/are the best alternative(s) for migration.
The options, which are specifically focused on in this document include:
Migration to Windows 2000 on the Desktop and Laptop
Migration to Windows XP on the Desktop and Laptop
Migration to Office 2000 on the desktop and laptop
Migration to Office XP on the desktop and laptop
Migration to another vendor's operating system on the desktop and laptop
Migration to another vendor's office suite on the desktop and laptop
Migration to Windows 2000 Server as the Network Operating System
Migration to Windows.NET Server as the Network Operating System
Migration to another vendor's Network Operating System
Migration of all or part of our environment to Thin Client environment
Do Nothing
Factors, which must be weighed in making a determination include:
The Business needs of the agency
The cost to develop effective training for staff
The cost in time to actually train both technical staff and users
The cost to replace desktops/laptops/servers that will not function under new product releases
The cost in staff time to perform the physical migration
The cost effectiveness of rebuilding a device versus upgrading the device
The cost to migrate other related software to supported versions
The cost to migrate applications to the new environment
The cost to rebuild applications or purchase new software where existing cannot be migrated
Availability of support for each of the environments impacted by the proposed change
The cost to migrate information
The impacts of phased migrations
Risks of undertaking such a project
Benefits of undertaking such a project
Features gained
Features lost
The risks and cost of failing to act
Time
While all of these factors could not be assessed in the time given to complete this document, the information is an honest assessment of the factors that could be measured at this time.
Evaluating the Options:
Migration to Windows 2000 on the Desktop and Laptop
Windows 2000 is a desktop operating system. We would be replacing the existing Windows NT desktop operating system with this product.
50 - 55% of existing desktops are not capable of running Windows 2000.
Our hardware vendor (Dell) will not guarantee availability of devices able to run Windows NT beyond June 2002.
Industry indicates more cost effective to replace devices than to upgrade existing
standard software should run in this environment, some upgrades and testing should be conducted
Some applications may require modifications
Software/Hardware exceptions run a high risk of failing in this environment, particularly DOS based products.
Exception process warns of possibility and that BEITA is not obligated to make them work.
Training will be required for both technical staff and users.
Images for the new desktop OS would need to be created.
Development and testing for optimal configurations is a requirement.
Windows 2000 has been superseded by the new release of the desktop operating system called Windows XP.
More granular administration would allow for granting of some administrative functions to ITC's. This would require a project to develop a standard list of functions all ITC's would support.
Gartner is projecting support for Windows 2000 on the desktop into 2004. This is not a guarantee as Microsoft can change its support structure at will.
Windows 2000 has been shown to be a more stable operating system than Windows NT.
Windows 2000 will allow us to continue to run the existing office suite.
Windows 2000 provides for improved power management and plug-n-play features for laptop devices. This would allow us to reduce the number images to be supported.
Windows CE 3.5 requires Windows 2000/XP in order to function correctly. Implementation would reduce costs to customers using Windows CE PDAs.
Windows 2000 eliminates 7.8 Gigabyte partition limitation on hard disks which has caused difficulties and additional work related to SMS pushes.
Windows 2000 provides for self healing applications in conjunction with Office 2000.
Migration to Windows XP on the Desktop and Laptop
Windows XP is Microsoft's most current desktop operating system. We would be replacing the existing Windows NT desktop operating system with this product.
50 - 55% of existing desktops are not capable of running Windows 2000.
Our hardware vendor (Dell) will not guarantee availability of devices able to run Windows NT beyond June 2002.
Industry indicates more cost effective to replace devices than to upgrade existing.
Software/Hardware exceptions run a high risk of failing in this environment, particularly DOS based products.
Exception process warns of possibility and that BEITA is not obligated to make it work.
Training will be required for both technical staff and users.
Images for the new desktop OS would need to be created.
Development and testing for optimal configurations is a requirement.
Windows XP is the most current version of Microsoft's desktop operating system. By going directly to it, we reduce costs by avoiding an extra migration.
More granular administration would allow for granting of some administrative functions to ITC's. This would require a project to develop a standard list of functions all ITC's would support.
Gartner currently is projecting support for Windows XP beyond 2004. This is not a guarantee as Microsoft can change its support structure at will.
Windows XP has been shown to be a more stable operating system than Windows NT.
It is uncertain if Windows XP will allow us to continue to run the existing desktop office suite. There are reports of successes and failures on Microsoft Technet.
Windows XP provides for improved power management and plug-n-play features for laptop devices. This would allow the to reduce the number of desktop images that must be maintained.
Windows CE 3.5 requires Windows 2000/XP in order to function correctly. Implementation would reduce costs to customers using Windows CE PDA's.
Windows XP eliminates the 7.8 Gigabyte partition limitation on hard disks which has caused difficulties and additional work related to SMS pushes.
Windows XP provides for self healing applications in conjuntion with Office 2000/XP.
As a brand new release, we would want to wait a period of time for patches before deploying across the agency.
Giga, Gartner and other industry analysts highly recommend the Windows XP product.
According to Giga, Gartner and others Windows XP will lower the cost of supporting the desktop.
Windows XP supports the concept of mobile profiles, making it easier for a user to move from device to device.
Windows XP allows switching of users, even if another user is currently logged on.
Vendors may begin to require this product as the lowest common denominator.
While other vendors have indicated that they intend to support Windows XP, some testing of software and applications will be required, and some additional software upgrades may be required.
We will need to explore security issues with this product.
We will need to examine how product activation impacts development of images. Product Activation is a means of preventing software piracy.
We will need to explore the auto update feature of this product.
Migration to Office 2000 on the Desktop and Laptop
Office 2000 is a desktop office suite comprised of Microsoft Word, Excel and Access. We would be replacing the existing Office 97 office suite with this product.
50 - 55% of existing desktops are not capable of running Office 2000.
Industry indicates more cost effective to replace devices than to upgrade existing.
Most existing software will function with Office 2000. There are some exceptions.
At least one application developed (SWAMP) will need modifications related to the implementation of this product.
Existing Microsoft Access applications may have difficulty migrating due to a new file structure in this version of the product.
Training will need to be provided to both Technical staff and users, to ensure quality installation and the ability to take advantage of new features.
Time will need to be allocated to ensure proper functioning of existing applications.
Time will need to be allocated for development of optimal configuration of product and images.
This version of the product has been superseded by the release of Office XP.
Implementation of this version will result in an extra migration needing to be completed.
There are no current projections for how long this version of the product will be supported.
This product should be reviewed and compared to agency business needs to see if there is value to the agency in adding them.
Basic functionality remains essentially the same and should minimize training in these areas.
Office 2000 allows for output in both HTML and XML formats, as well as traditional formats.
Office 2000 supports the concept of self healing applications.
Migration to Office XP on the Desktop and Laptop
Office XP is a desktop office suite comprised of Microsoft Word, Excel and Access. We would be replacing the existing Office 97 office suite with this product.
50 - 55% of existing desktops are not capable of running Office XP.
Industry indicates more cost effective to replace devices than to upgrade existing.
Most existing software will function with Office XP. There are some exceptions.
At least one application developed (SWAMP) will need modifications related to the implementation of this product and others that integrate with the office suite should be checked.
Existing Microsoft Access applications may have difficulty migrating due to a new file structure in this version of the product.
Training will need to be provided to both Technical staff and users, to ensure quality installation and the ability to take advantage of new features.
Time will need to be allocated to ensure proper functioning of existing applications.
Time will need to be allocated for development of optimal configuration of product and images.
Implementation of this version avoids an extra migration step.
There are no current projections for how long this version of the product will be supported.
This product should be reviewed and compared to agency business needs to see if there is value to the agency in adding them.
Basic functionality remains essentially the same and should minimize training in these areas.
Office XP allows for output in both HTML and XML formats, as well as traditional formats.
Office XP supports the concept of self healing applications.
Office XP provides more extensive collaboration tools.
Office XP provides for strong programmable capabilities that we would need to examine and develop standards for.
Beginning with this version of the product, we will incur annual licensing fees.
We will need to examine how product activation impacts development of images. Product Activation is a means of preventing software piracy.
We will need to explore security issues with this product.
As a brand new release, we would want to wait a period of time for patches before deploying across the agency.
Migration to an Alternate Operating System on the Desktop and Laptop
With the advent of open source software development, have come a number of seemingly low cost alternatives to the Microsoft products which are currently prevalent in Wisconsin State Government. Probably the most well know of these is Linux in its various flavors. Linux is a desktop operating system. There are a number of vendors who produce Linux versions because of the rules related to Open Source software development.
Open source software tends to have fairly low initial software costs.
Product support for our standard software and hardware is uneven. Some vendors support some flavors, others another.
Need to closely examine how viable the vendor of this operating system is.
ESRI does not develop products for Linux and to date will not commit to doing so.
Oracle provides some support for Linux, but it is unclear how well.
A number of applications developed at the will not function in this environment, which would mean redesign and redevelopment in a tool that would function.
We would be forced to migrate to a whole new Office Suite, if we were to adopt this operating system.
We may need to redesign things like letter head and forms to run in a product on this perating system.
We would need to create whole new training programs for staff and require them to take this training, in order for them to attain proficiency in the new operating system.
We would need to allocate time for technical staff to become proficient in managing this operating system.
We would need to take time to determine optimal configurations and develop images for this environment.
We would need to find a replacement for Site Server and a number of our web development tools, which are Microsoft centric at this time.
It is almost a guarantee that most of the Software Exception requests will not function in this environment and most certainly not the DOS applications.
Cost estimates for conversion work, training, deployment and lost hours would most likely be in the Millions of dollars. We would need to balance this against the savings in licensing fees and the long term viability of the vendor.
Migration to an Alternate Office Suite on the Desktop and Laptop
Today there are a number of alternatives to the Microsoft products which are currently prevalent in Wisconsin State Government. In the realm of alternate office suites, we have more choices in general terms, many of them even capable of running in a Microsoft Operating System.
Open source software tends to have fairly low initial software costs.
Need to closely examine how viable the software and the vendor of the product are. For example: Sun produces Star Office. Sun is a very viable company in and of itself, however they earn no revenue on Star Office. If push comes to shove, this most likely would be one of the first things they drop.
A number of our applications are integrated with the Microsoft Office Suite. Moving to Star Office or Word Perfect would require us to redevelop those portions of our applications integrated with the Office Suite.
It is unknown at this time, what support there may be for integrating alternate Office Suites with our existing tools, such as Oracle, PowerBuilder and Visual Interdev.
We would need to examine conversion of existing documents, forms, spread sheets and single user databases from the Microsoft Office Suite to the new Office Suite.
We would need to create whole new training programs for staff and require them to take this training, in order for them to attain proficiency in the new office suite.
We would need to allocate time for technical staff to become proficient in managing this office suite.
We would need to take time to determine optimal configurations and develop images for this environment.
We would need to examine the impacts of making such a decision on our business partners. While selecting WordPerfect would simplify communicating with EPA, selecting Star Office could potentially alienate us from every business partner in terms of our ability to share documents.
Making this change to our desktop office suite will cost large sums of money in converting existing documents and applications, training, and set up. It will require an extended period of time to accomplish. We would need to balance these costs against any potential savings in licensing fees and the long term viability of the vendor.
Migration to Windows 2000 Server as the Network Operating System
Windows 2000 Server is the most current "production" operating system produced by Microsoft. If implemented, it would replace Windows NT Server within the .
Windows 2000 Server is a substantially more stable product than Windows NT Server.
Windows 2000 Server provides all the functionality of Windows NT Server and expands upon it.
Microsoft has announced a new Network Operating System release is currently in beta testing. No release date has been announced.
Moving to Windows 2000 Server will require implementation of Active Directory.
The Enterprise desires to role out Active Directory in a uniform manner throughout state government. This project is not currently funded.
Several agencies are proceeding with implementation of Active Directory in advance of the Enterprise.
Servers should be migrated to Windows 2000 before the desktop Operating System is upgraded to avoid additional stops/modifications to the desktop at a later date.
Four technical staff are already trained in Windows 2000 Server.
Existing servers should only require minimal upgrades in the area of memory in order to be migrated to Windows 2000 Server.
This product allows for improved file and print services as compared to Windows NT.
Our existing (Domain Name Services) translates directly to Windows 2000 Server. In addition, Windows 2000 Server provides more robust support for DNS and DHCP while are integral parts of the 's existing network.
This product continues to support Outlook Web Access and improves the interface for this tool.
This product continues to support both IIS and Site Server which are part of our Internet and Intranet environments.
We know that our side Oracle and ESRI tools will operate within this environment.
Migration to Another Vendor's Network Operating System
There are several other Network Operating Systems that could be chosen, including various Unix and Linux flavors. Each of them carries their own licensing requirements and each would need to be examined against our other existing Network Services for viability. Following is a brief over view.
Migration of All or Part of Our Environment to Thin Client Services
A thin client environment is focused on maintaining less software and data at the client. This reduces the investment required in desktop software. Obviously, we would need to compensate on the server side.
Do Nothing
Chosing to do nothing at this time appears to save the agency money, and it potentially does in the short term. Eventually, due to software or hardware failure we would be forced into doing something. The following points help to evaluate the concerns of doing nothing.
The Hidden Costs of Phased Migrations
Recommendation:
We believe that the first step in migrating our existing Server and Desktop Operating System and Desktop Office Suite is to focus on the environment that we felt most needed to have vendor support available on a continuing basis. As our Network Servers provide connectivity, email and data services to the agency, we felt that they must receive first priority in any upgrade scenario. As such we recommend that first priority be given to migrate all Windows NT Servers to Windows 2000. This will require implementation of Active Directory as well. Most of these servers only need the Windows 2000 server version, although a few would need to be set up for Windows 2000 Advanced Server because of the number of processors they contain. As part of this we are recommending that we select Upgrade Advantage for these servers.
We also recommend that this agency pursue the development of a new PBB for purchase of several devices with Windows XP, set up and testing of applications and standard software in the new Operating System and with the proposed office suite. We believe that it is important that this testing be undertaken yet this fiscal year, if at all possible. This information will serve us well in determining what actual work would need to be completed in order to migrate to this operating system. The information gathered will be valuable in further assessing how we will deal with the impending lack of support for Windows NT on newly purchased desktop and laptop devices. We do not believe there is any gain to implementing Windows 2000, and experts including Giga and Gartner both recommend bypassing 2000 if you have not already begun implementation on the desktop.
Our third recommendation is that a mandatory PBB be created and executed in the new Fiscal Year to Research Windows Terminal Servers, and in particular Citrix. Along with assessing the technical viability of the product within the , this project will develop a detailed cost benefit analysis of Citrix and Windows Terminal Server. The project would need to test existing applications and software. It has been suggested that we may want to require software exceptions be run from a Citrix server as well, to minimize costs to the desktop. It would also have to look at the makeup of staff and their requirements for a desktop. While Citrix would require investment in servers and disk space, we could reduce costs for the desktop in terms of needing less powerful machines and lengthening the life of a device.
Our fourth recommendation is to place a moratorium on purchase of new devices, once our vendor (Dell) can no longer provide devices capable of running NT, until such time as we have completed the work in our second recommendation. We would encourage those who have a need to replace defective equipment look to the devices being surplused by other programs as a means of maintaining basic functionality until such time as the evaluation of the second recommendation and possibly the third recommendation.
Ahhh, 508. It appears to be my saviour here also. I'm a geek in a M$ world where I work. I actually get laughed at sometimes, simply because I suggest we can save a boatload of money by moving to open-source. Oh well...
One possible solution to the flash editor thing is to use something like k-illustrator to make your sprites and Flash under vmware or wine to put it together. Oher than that, I think your hosed. Unless we can get a bunch of hackers to write an open source SWF editor.
QNX kicks ass. I've installed it on a 16mb 75mhz Packard Hell box I had laying around (not sure where the hell that came from...). Beautiful OS, one of the best I think I've ever seen. Small, fast, hell, I'm thinking about putting it on a bigger box and trying it as a desktop for a while.
I've submitted over 100 stories, all of them relevant(sp?) to this site. I've _never_ gotten a stry posted. I don't want to hear any gay troll shit about my nick either.
I got offered Charter Pipeline to replace my Charter@Home connection. It appears to start at 29.95/m, although you need a different modem and cable filter. I'm not sure if they're offering it in all areas though. It should have been on the postcard. Did you read the whole thing?
mod parent up! This says exactly what I've been talking about to my various managers for years. The big problem is, the argument is starting to fall apart. Win2k is almost acceptable from a technical viewpoint, so you need to get into more detail. Exec's don't want to hear detail, their eyes glaze over. At that point, you lose. I'm on the IT Architecture team here now, and I'm finding it difficult to even get the rest of the team to listen. grrrrr. I did manage to get them to consider allowing us to install a Linux box running Oracle 9iAS though, so I think I 'm getting a win. It occurs to me that we (us geeks and sysadmin types) are the only people really selling Linux, our counterparts in M$ land are professional sales people. We kick their ass technically, don't we? No wonder it's tough for us to beat them in the board room, closing the sale so to speak.
I think MAME for xbox will get a chance. From the front page of your link:
"Although legal restrains prohibit Otaku from releasing the current build to anyone but registered XBox Developers, he assures us that we haven't heard the last of MAME for the XBox..."
This tells me that the dude just held back because of the NDA for developers, prior to the release of xbox. Personally, I'll buy one ONLY if I can find a Linux port for it. I'm also curious as to what would keep us from making an xbox emulator so we can run xbox games directly on our PC's. Anyone interested in doing that?
I want Heinlein's Luna City! That would be so extremely cool. More on topic, what about D.D. Harriman? The series of stories where the government isn't really involved in space travel at all. It's good ol' capitalism for Heinlein, thank you. There HAS to be a way to wrest the development of space out of the governments hands. Maybe if we all started a whisper campaign that there's diamonds on the moon or something.
I've been wondering about that. I'm starting to become pear shaped also. Yet I excercise a lot. Like hiking the Wisconsin River bluffs around here. Push starting junky old sportsters. Moving the mouse around. Chasing (or running from) crazy bastards with rocket launchers. I've decided to eat less. Being round is no way to go through life, son.
cool. I'm going to Comdex in Chicago in the next couple of weeks, and I think I'll spend some time walking around the TradeCenter with my laptop. Might be very interesting to see what I can pickup. What's that you say? It's illegal to do that? Not my problem, I liken this to a publicly accessable park.
When I actually have time to watch TV, I really don't give a damn what particular channel I'm watching. It appears that the various networks really want us to know, though. The Discover channels seem to be the worst. It really pisses me off to be watching a show and to miss part of it due to the logo in the corner. Oh well, I'd rather play games or code anyway.
Bite my ass, you doofus troll. Besides, I use vi, not that abortion some people call an editor you obviously prefer. As far as programming my editor, fsck that, I'm lazy. I want someone else to create one for me.
Speaking about IDE's, I'm looking for a great PHP editor/IDE. I've been working with the Dreamweaver Ultradev extension for PHP, but I find it lacking. Normally, I work in Homesite, but a GUI editor like Dreamweaver is extremely nice to work in. Any suggestions out there?
What I saw was a small page set for a 640x480 window, with some pictures. No evident navigational aids, no obvious links. It looked pretty crappy to me. I dunno, I guess I was grumpy this morning.
Slashdot Mirror
It's used in Albion, WI. Redhat on older Gateway hardware. It sits right along side of the Win95 and Mac boxen. I'm pretty sure they're going to be installing it on the rest of the x86 boxen.
Actually, I am Jack's server.
Now, to stay on topic, I've been playing with the KDE desktops and I like it. I think Gnome is better looking, in the stock configuration, though.
Have you read the Cournty Love commentary? Basically, when a band gets signed, they end up in debt for around 2 million to the label. The CD sells 500,000 copies. THe band gets shit, the label profits something like 6.6 million. Your analogy is not even close. The only way bands make money is touring, t-shirts, and shit like that. I'm a musician. That DOES NOT mean I like to take it up the ass from major labels. All I really want to do is write music, perform it, and make a damn living doing it. Porbably one of the hardest careers a person could choose. I ended up being a sysadmin simply because I want to live like a human being, not like some depraved gypsy on a tour bus forever.
Since I'm just stating a new band, this looks like the best possible opportunity for us. Thank you.
Does anyone have good info about setting up one of these? Yes, I'll go an look around on Google, I want /. info first. I mean, it's not just getting an 802.11b transciever and proclaiming to the world "Here I am!". You need a way to control users access, billing stuff, how do you put it on their end? Do you sell them the transciever, rent it, make them buy there own? How do you decide where you wanna go first?
I'm assuming rural here, since most urban places have broadband available. How about selling to businesses? If you can't tell, I'm pretty interested in doing this.
First off, before the trolls get to it, no, *BSD IS NOT DYING. Ok, I'm donme with that part.
I've been using FreeBSD since early 1994 and have grown up with ti, so to speak. Even back then, I tried Linux and ended up learning FreeBSD. I'm really glad to see people writing for newbies.
Looks like I might be able to sneak PHP in here now. I've been using it for my own web development projects for a few years now and all I can say is, it kicks ass. Congrats to the PHP crew!
.asp and can do virtually anything you can do with java, except for client side stuff like applets. It's extremely fast and pretty straight forward to learn. Can you tell I like it?
If you're trying to decide which direction to go in web development, take a real close look at PHP. It totally smokes
The following is the result of research into various OS and office suites. THIS IS NOT MY OPINION! It's the opinion of a commitee I work with. I deleted the agencies name to protect my ass. This is what we deal with if we want to try and convert the Gov to an OSS solution.
.NET Server. We can anticipate similar desupport notices and issues for Windows NT Server in the next six months to one year.
.NET Server as the Network Operating System
/Hardware exceptions run a high risk of failing in this environment, particularly DOS based products.
Technical Evaluation of Alternatives for Upgrading and Migrating the 's Desktop Operating System and Office Suite and Network Server Operating System
The Issues: Since the deployment of Windows NT approximately 6 years ago and Office 97 approximately 3 years ago, Microsoft has released two new versions of the desktop operating system and the office suite. It is anticipated that Microsoft will terminate support for our existing environment in the near future. It has also been announced that our desktop hardware vendor will discontinue support for Windows NT on laptops beginning in June of 2002 and for desktops most likely by June of 2002. It is expected that other vendors will follow suit, after Microsoft makes its announcement. Vendor support of our tools is an important part of being able to maintain our environment in its best form. It allows us to resolve issues more quickly, and when there isn't a ready solution, it is a means by which we can get the vendor to assist us in resolving our issues.
We face a similar issue for the current version of our network operating system, which is Windows NT Server. There currently is one newer version of this operating system on the market, which is called Windows 2000 Server and technically there are three flavors of this product. Microsoft has announced that it is currently beta testing another version called Windows
In addition to the normal cycle of product upgrades and desupport notices, we will be faced with making licensing choices in how we choose to license Microsoft products in the future. The focus of this paper is on the technical aspects of these announcements and their impacts. Issues of licensing and funding are items, which are to be explored by , however this team is acutely aware of the current fiscal situation facing this agency and has made recommendations with this situation in mind.
The Scope of This Document: The purpose of this document is to outline the technical criteria on which decisions for migration to a new version of the desktop operating system, desktop office suite, and network operating system can be made. In addition, this document will provide a recommendation on what BEITA believes is/are the best alternative(s) for migration.
The options, which are specifically focused on in this document include:
Migration to Windows 2000 on the Desktop and Laptop
Migration to Windows XP on the Desktop and Laptop
Migration to Office 2000 on the desktop and laptop
Migration to Office XP on the desktop and laptop
Migration to another vendor's operating system on the desktop and laptop
Migration to another vendor's office suite on the desktop and laptop
Migration to Windows 2000 Server as the Network Operating System
Migration to Windows
Migration to another vendor's Network Operating System
Migration of all or part of our environment to Thin Client environment
Do Nothing
Factors, which must be weighed in making a determination include:
The Business needs of the agency
The cost to develop effective training for staff
The cost in time to actually train both technical staff and users
The cost to replace desktops/laptops/servers that will not function under new product releases
The cost in staff time to perform the physical migration
The cost effectiveness of rebuilding a device versus upgrading the device
The cost to migrate other related software to supported versions
The cost to migrate applications to the new environment
The cost to rebuild applications or purchase new software where existing cannot be migrated
Availability of support for each of the environments impacted by the proposed change
The cost to migrate information
The impacts of phased migrations
Risks of undertaking such a project
Benefits of undertaking such a project
Features gained
Features lost
The risks and cost of failing to act
Time
While all of these factors could not be assessed in the time given to complete this document, the information is an honest assessment of the factors that could be measured at this time.
Evaluating the Options:
Migration to Windows 2000 on the Desktop and Laptop
Windows 2000 is a desktop operating system. We would be replacing the existing Windows NT desktop operating system with this product.
50 - 55% of existing desktops are not capable of running Windows 2000.
Our hardware vendor (Dell) will not guarantee availability of devices able to run Windows NT beyond June 2002.
Industry indicates more cost effective to replace devices than to upgrade existing
standard software should run in this environment, some upgrades and testing should be conducted
Some applications may require modifications
Software/Hardware exceptions run a high risk of failing in this environment, particularly DOS based products.
Exception process warns of possibility and that BEITA is not obligated to make them work.
Training will be required for both technical staff and users.
Images for the new desktop OS would need to be created.
Development and testing for optimal configurations is a requirement.
Windows 2000 has been superseded by the new release of the desktop operating system called Windows XP.
More granular administration would allow for granting of some administrative functions to ITC's. This would require a project to develop a standard list of functions all ITC's would support.
Gartner is projecting support for Windows 2000 on the desktop into 2004. This is not a guarantee as Microsoft can change its support structure at will.
Windows 2000 has been shown to be a more stable operating system than Windows NT.
Windows 2000 will allow us to continue to run the existing office suite.
Windows 2000 provides for improved power management and plug-n-play features for laptop devices. This would allow us to reduce the number images to be supported.
Windows CE 3.5 requires Windows 2000/XP in order to function correctly. Implementation would reduce costs to customers using Windows CE PDAs.
Windows 2000 eliminates 7.8 Gigabyte partition limitation on hard disks which has caused difficulties and additional work related to SMS pushes.
Windows 2000 provides for self healing applications in conjunction with Office 2000.
Migration to Windows XP on the Desktop and Laptop
Windows XP is Microsoft's most current desktop operating system. We would be replacing the existing Windows NT desktop operating system with this product.
50 - 55% of existing desktops are not capable of running Windows 2000.
Our hardware vendor (Dell) will not guarantee availability of devices able to run Windows NT beyond June 2002.
Industry indicates more cost effective to replace devices than to upgrade existing.
Software
Exception process warns of possibility and that BEITA is not obligated to make it work.
Training will be required for both technical staff and users.
Images for the new desktop OS would need to be created.
Development and testing for optimal configurations is a requirement.
Windows XP is the most current version of Microsoft's desktop operating system. By going directly to it, we reduce costs by avoiding an extra migration.
More granular administration would allow for granting of some administrative functions to ITC's. This would require a project to develop a standard list of functions all ITC's would support.
Gartner currently is projecting support for Windows XP beyond 2004. This is not a guarantee as Microsoft can change its support structure at will.
Windows XP has been shown to be a more stable operating system than Windows NT.
It is uncertain if Windows XP will allow us to continue to run the existing desktop office suite. There are reports of successes and failures on Microsoft Technet.
Windows XP provides for improved power management and plug-n-play features for laptop devices. This would allow the to reduce the number of desktop images that must be maintained.
Windows CE 3.5 requires Windows 2000/XP in order to function correctly. Implementation would reduce costs to customers using Windows CE PDA's.
Windows XP eliminates the 7.8 Gigabyte partition limitation on hard disks which has caused difficulties and additional work related to SMS pushes.
Windows XP provides for self healing applications in conjuntion with Office 2000/XP.
As a brand new release, we would want to wait a period of time for patches before deploying across the agency.
Giga, Gartner and other industry analysts highly recommend the Windows XP product.
According to Giga, Gartner and others Windows XP will lower the cost of supporting the desktop.
Windows XP supports the concept of mobile profiles, making it easier for a user to move from device to device.
Windows XP allows switching of users, even if another user is currently logged on.
Vendors may begin to require this product as the lowest common denominator.
While other vendors have indicated that they intend to support Windows XP, some testing of software and applications will be required, and some additional software upgrades may be required.
We will need to explore security issues with this product.
We will need to examine how product activation impacts development of images. Product Activation is a means of preventing software piracy.
We will need to explore the auto update feature of this product.
Migration to Office 2000 on the Desktop and Laptop
Office 2000 is a desktop office suite comprised of Microsoft Word, Excel and Access. We would be replacing the existing Office 97 office suite with this product.
50 - 55% of existing desktops are not capable of running Office 2000.
Industry indicates more cost effective to replace devices than to upgrade existing.
Most existing software will function with Office 2000. There are some exceptions.
At least one application developed (SWAMP) will need modifications related to the implementation of this product.
Existing Microsoft Access applications may have difficulty migrating due to a new file structure in this version of the product.
Training will need to be provided to both Technical staff and users, to ensure quality installation and the ability to take advantage of new features.
Time will need to be allocated to ensure proper functioning of existing applications.
Time will need to be allocated for development of optimal configuration of product and images.
This version of the product has been superseded by the release of Office XP.
Implementation of this version will result in an extra migration needing to be completed.
There are no current projections for how long this version of the product will be supported.
This product should be reviewed and compared to agency business needs to see if there is value to the agency in adding them.
Basic functionality remains essentially the same and should minimize training in these areas.
Office 2000 allows for output in both HTML and XML formats, as well as traditional formats.
Office 2000 supports the concept of self healing applications.
Migration to Office XP on the Desktop and Laptop
Office XP is a desktop office suite comprised of Microsoft Word, Excel and Access. We would be replacing the existing Office 97 office suite with this product.
50 - 55% of existing desktops are not capable of running Office XP.
Industry indicates more cost effective to replace devices than to upgrade existing.
Most existing software will function with Office XP. There are some exceptions.
At least one application developed (SWAMP) will need modifications related to the implementation of this product and others that integrate with the office suite should be checked.
Existing Microsoft Access applications may have difficulty migrating due to a new file structure in this version of the product.
Training will need to be provided to both Technical staff and users, to ensure quality installation and the ability to take advantage of new features.
Time will need to be allocated to ensure proper functioning of existing applications.
Time will need to be allocated for development of optimal configuration of product and images.
Implementation of this version avoids an extra migration step.
There are no current projections for how long this version of the product will be supported.
This product should be reviewed and compared to agency business needs to see if there is value to the agency in adding them.
Basic functionality remains essentially the same and should minimize training in these areas.
Office XP allows for output in both HTML and XML formats, as well as traditional formats.
Office XP supports the concept of self healing applications.
Office XP provides more extensive collaboration tools.
Office XP provides for strong programmable capabilities that we would need to examine and develop standards for.
Beginning with this version of the product, we will incur annual licensing fees.
We will need to examine how product activation impacts development of images. Product Activation is a means of preventing software piracy.
We will need to explore security issues with this product.
As a brand new release, we would want to wait a period of time for patches before deploying across the agency.
Migration to an Alternate Operating System on the Desktop and Laptop
With the advent of open source software development, have come a number of seemingly low cost alternatives to the Microsoft products which are currently prevalent in Wisconsin State Government. Probably the most well know of these is Linux in its various flavors. Linux is a desktop operating system. There are a number of vendors who produce Linux versions because of the rules related to Open Source software development.
Open source software tends to have fairly low initial software costs.
Product support for our standard software and hardware is uneven. Some vendors support some flavors, others another.
Need to closely examine how viable the vendor of this operating system is.
ESRI does not develop products for Linux and to date will not commit to doing so.
Oracle provides some support for Linux, but it is unclear how well.
A number of applications developed at the will not function in this environment, which would mean redesign and redevelopment in a tool that would function.
We would be forced to migrate to a whole new Office Suite, if we were to adopt this operating system.
We may need to redesign things like letter head and forms to run in a product on this perating system.
We would need to create whole new training programs for staff and require them to take this training, in order for them to attain proficiency in the new operating system.
We would need to allocate time for technical staff to become proficient in managing this operating system.
We would need to take time to determine optimal configurations and develop images for this environment.
We would need to find a replacement for Site Server and a number of our web development tools, which are Microsoft centric at this time.
It is almost a guarantee that most of the Software Exception requests will not function in this environment and most certainly not the DOS applications.
Cost estimates for conversion work, training, deployment and lost hours would most likely be in the Millions of dollars. We would need to balance this against the savings in licensing fees and the long term viability of the vendor.
Migration to an Alternate Office Suite on the Desktop and Laptop
Today there are a number of alternatives to the Microsoft products which are currently prevalent in Wisconsin State Government. In the realm of alternate office suites, we have more choices in general terms, many of them even capable of running in a Microsoft Operating System.
Open source software tends to have fairly low initial software costs.
Need to closely examine how viable the software and the vendor of the product are. For example: Sun produces Star Office. Sun is a very viable company in and of itself, however they earn no revenue on Star Office. If push comes to shove, this most likely would be one of the first things they drop.
A number of our applications are integrated with the Microsoft Office Suite. Moving to Star Office or Word Perfect would require us to redevelop those portions of our applications integrated with the Office Suite.
It is unknown at this time, what support there may be for integrating alternate Office Suites with our existing tools, such as Oracle, PowerBuilder and Visual Interdev.
We would need to examine conversion of existing documents, forms, spread sheets and single user databases from the Microsoft Office Suite to the new Office Suite.
We would need to create whole new training programs for staff and require them to take this training, in order for them to attain proficiency in the new office suite.
We would need to allocate time for technical staff to become proficient in managing this office suite.
We would need to take time to determine optimal configurations and develop images for this environment.
We would need to examine the impacts of making such a decision on our business partners. While selecting WordPerfect would simplify communicating with EPA, selecting Star Office could potentially alienate us from every business partner in terms of our ability to share documents.
Making this change to our desktop office suite will cost large sums of money in converting existing documents and applications, training, and set up. It will require an extended period of time to accomplish. We would need to balance these costs against any potential savings in licensing fees and the long term viability of the vendor.
Migration to Windows 2000 Server as the Network Operating System
Windows 2000 Server is the most current "production" operating system produced by Microsoft. If implemented, it would replace Windows NT Server within the .
Windows 2000 Server is a substantially more stable product than Windows NT Server.
Windows 2000 Server provides all the functionality of Windows NT Server and expands upon it.
Microsoft has announced a new Network Operating System release is currently in beta testing. No release date has been announced.
Moving to Windows 2000 Server will require implementation of Active Directory.
The Enterprise desires to role out Active Directory in a uniform manner throughout state government. This project is not currently funded.
Several agencies are proceeding with implementation of Active Directory in advance of the Enterprise.
Servers should be migrated to Windows 2000 before the desktop Operating System is upgraded to avoid additional stops/modifications to the desktop at a later date.
Four technical staff are already trained in Windows 2000 Server.
Existing servers should only require minimal upgrades in the area of memory in order to be migrated to Windows 2000 Server.
This product allows for improved file and print services as compared to Windows NT.
Our existing (Domain Name Services) translates directly to Windows 2000 Server. In addition, Windows 2000 Server provides more robust support for DNS and DHCP while are integral parts of the 's existing network.
This product continues to support Outlook Web Access and improves the interface for this tool.
This product continues to support both IIS and Site Server which are part of our Internet and Intranet environments.
We know that our side Oracle and ESRI tools will operate within this environment.
Migration to Another Vendor's Network Operating System
There are several other Network Operating Systems that could be chosen, including various Unix and Linux flavors. Each of them carries their own licensing requirements and each would need to be examined against our other existing Network Services for viability. Following is a brief over view.
Migration of All or Part of Our Environment to Thin Client Services
A thin client environment is focused on maintaining less software and data at the client. This reduces the investment required in desktop software. Obviously, we would need to compensate on the server side.
Do Nothing
Chosing to do nothing at this time appears to save the agency money, and it potentially does in the short term. Eventually, due to software or hardware failure we would be forced into doing something. The following points help to evaluate the concerns of doing nothing.
The Hidden Costs of Phased Migrations
Recommendation:
We believe that the first step in migrating our existing Server and Desktop Operating System and Desktop Office Suite is to focus on the environment that we felt most needed to have vendor support available on a continuing basis. As our Network Servers provide connectivity, email and data services to the agency, we felt that they must receive first priority in any upgrade scenario. As such we recommend that first priority be given to migrate all Windows NT Servers to Windows 2000. This will require implementation of Active Directory as well. Most of these servers only need the Windows 2000 server version, although a few would need to be set up for Windows 2000 Advanced Server because of the number of processors they contain. As part of this we are recommending that we select Upgrade Advantage for these servers.
We also recommend that this agency pursue the development of a new PBB for purchase of several devices with Windows XP, set up and testing of applications and standard software in the new Operating System and with the proposed office suite. We believe that it is important that this testing be undertaken yet this fiscal year, if at all possible. This information will serve us well in determining what actual work would need to be completed in order to migrate to this operating system. The information gathered will be valuable in further assessing how we will deal with the impending lack of support for Windows NT on newly purchased desktop and laptop devices. We do not believe there is any gain to implementing Windows 2000, and experts including Giga and Gartner both recommend bypassing 2000 if you have not already begun implementation on the desktop.
Our third recommendation is that a mandatory PBB be created and executed in the new Fiscal Year to Research Windows Terminal Servers, and in particular Citrix. Along with assessing the technical viability of the product within the , this project will develop a detailed cost benefit analysis of Citrix and Windows Terminal Server. The project would need to test existing applications and software. It has been suggested that we may want to require software exceptions be run from a Citrix server as well, to minimize costs to the desktop. It would also have to look at the makeup of staff and their requirements for a desktop. While Citrix would require investment in servers and disk space, we could reduce costs for the desktop in terms of needing less powerful machines and lengthening the life of a device.
Our fourth recommendation is to place a moratorium on purchase of new devices, once our vendor (Dell) can no longer provide devices capable of running NT, until such time as we have completed the work in our second recommendation. We would encourage those who have a need to replace defective equipment look to the devices being surplused by other programs as a means of maintaining basic functionality until such time as the evaluation of the second recommendation and possibly the third recommendation.
Ahhh, 508. It appears to be my saviour here also. I'm a geek in a M$ world where I work. I actually get laughed at sometimes, simply because I suggest we can save a boatload of money by moving to open-source. Oh well...
One possible solution to the flash editor thing is to use something like k-illustrator to make your sprites and Flash under vmware or wine to put it together. Oher than that, I think your hosed. Unless we can get a bunch of hackers to write an open source SWF editor.
That is one horrible flash intro at KPMG. No wonder they want people to get permission to link to it.
QNX kicks ass. I've installed it on a 16mb 75mhz Packard Hell box I had laying around (not sure where the hell that came from...). Beautiful OS, one of the best I think I've ever seen. Small, fast, hell, I'm thinking about putting it on a bigger box and trying it as a desktop for a while.
I've submitted over 100 stories, all of them relevant(sp?) to this site. I've _never_ gotten a stry posted. I don't want to hear any gay troll shit about my nick either.
I got offered Charter Pipeline to replace my Charter@Home connection. It appears to start at 29.95/m, although you need a different modem and cable filter. I'm not sure if they're offering it in all areas though. It should have been on the postcard. Did you read the whole thing?
I want a job there. I'm mandated to use M$ servers. I was lucky to get them to let me install Win2k even. groan
mod parent up! This says exactly what I've been talking about to my various managers for years. The big problem is, the argument is starting to fall apart. Win2k is almost acceptable from a technical viewpoint, so you need to get into more detail. Exec's don't want to hear detail, their eyes glaze over. At that point, you lose. I'm on the IT Architecture team here now, and I'm finding it difficult to even get the rest of the team to listen. grrrrr. I did manage to get them to consider allowing us to install a Linux box running Oracle 9iAS though, so I think I 'm getting a win. It occurs to me that we (us geeks and sysadmin types) are the only people really selling Linux, our counterparts in M$ land are professional sales people. We kick their ass technically, don't we? No wonder it's tough for us to beat them in the board room, closing the sale so to speak.
I think MAME for xbox will get a chance. From the front page of your link:
"Although legal restrains prohibit Otaku from releasing the current build to anyone but registered XBox Developers, he assures us that we haven't heard the last of MAME for the XBox..."
This tells me that the dude just held back because of the NDA for developers, prior to the release of xbox. Personally, I'll buy one ONLY if I can find a Linux port for it. I'm also curious as to what would keep us from making an xbox emulator so we can run xbox games directly on our PC's. Anyone interested in doing that?
I want Heinlein's Luna City! That would be so extremely cool. More on topic, what about D.D. Harriman? The series of stories where the government isn't really involved in space travel at all. It's good ol' capitalism for Heinlein, thank you. There HAS to be a way to wrest the development of space out of the governments hands. Maybe if we all started a whisper campaign that there's diamonds on the moon or something.
duh. Follow the link. Think physically, like a hard object.
I've been wondering about that. I'm starting to become pear shaped also. Yet I excercise a lot. Like hiking the Wisconsin River bluffs around here. Push starting junky old sportsters. Moving the mouse around. Chasing (or running from) crazy bastards with rocket launchers. I've decided to eat less. Being round is no way to go through life, son.
cool. I'm going to Comdex in Chicago in the next couple of weeks, and I think I'll spend some time walking around the TradeCenter with my laptop. Might be very interesting to see what I can pickup. What's that you say? It's illegal to do that? Not my problem, I liken this to a publicly accessable park.
What's even worse is when the URL is covered by the logo, thus making it unreadable.
When I actually have time to watch TV, I really don't give a damn what particular channel I'm watching. It appears that the various networks really want us to know, though. The Discover channels seem to be the worst. It really pisses me off to be watching a show and to miss part of it due to the logo in the corner. Oh well, I'd rather play games or code anyway.
Bite my ass, you doofus troll. Besides, I use vi, not that abortion some people call an editor you obviously prefer. As far as programming my editor, fsck that, I'm lazy. I want someone else to create one for me.
Speaking about IDE's, I'm looking for a great PHP editor/IDE. I've been working with the Dreamweaver Ultradev extension for PHP, but I find it lacking. Normally, I work in Homesite, but a GUI editor like Dreamweaver is extremely nice to work in. Any suggestions out there?
What I saw was a small page set for a 640x480 window, with some pictures. No evident navigational aids, no obvious links. It looked pretty crappy to me. I dunno, I guess I was grumpy this morning.