Hello everybody. So here at work we have an internet cafe where service is available by the hour. Right now all the systems are running windows xp, and so to maintain them we have been using the Windows SteadyState program, so that the computers can remain fully unlocked and usable for customers while also not needing to worry about them messing with it or infecting it with a virus, ect.
The way SteadyState works is after we have the system configured to how we like, the program creates a read-only backup image that it will boot from, so no changes are saved between reboots. It works but it is clumsy, difficult to maintain, and does not work with vista/7.
I've been charged with the task of figuring out a better system, and one that works with windows 7 so we can upgrade a number of our systems available. At that point we would have 3 different hardware configurations, Pentium4 with XP, Core2D with XP, and Core2D with 7.
So far what I've found and am currently trying to learn about is imagex and .wim files. I think what I'm trying to do, if it's possible, is create a single .wim image for each configuration, and have each system boot from this image every time. So to make changes or update the system, I would just have to work on one computer, image it, and copy that image to the other identical systems.
Things I need help with/don't know:
- Is it even possible to boot windows from a local read-only .wim image?
- each computer should have a unique network name, would that be possible using the same image (such as with windows deployment services [don't really know how that works or will be used at this point])?
- If I need a server to get this to work, i should be able to add a window 2003 or 2008 to that network, but it's still on 10/100 so i'd prefer not to boot from the network.
- as opposed to booting from the network, could I get the client to download a new .wim image over pxe (such as by manually selecting pxe boot from bios startup only to pull updated images) and then boot from the local drive?
Right now I've just finished downloading the windows AIK, so my current step is just creating a test .wim image.
This is well beyond the scope of my normal job description, but I'd really like to be able to get it working. I'm very new to windows server and deployment situations and most of what I know I've learned in the past two days, so any help or even links to read up on would be much appreciated!
Edit: is this even in the right section? I put it here because I had the integration with server 2003/2008 on my mind, but after reading it over I realize most of my questions are regarding local file access.
The way SteadyState works is after we have the system configured to how we like, the program creates a read-only backup image that it will boot from, so no changes are saved between reboots. It works but it is clumsy, difficult to maintain, and does not work with vista/7.
I've been charged with the task of figuring out a better system, and one that works with windows 7 so we can upgrade a number of our systems available. At that point we would have 3 different hardware configurations, Pentium4 with XP, Core2D with XP, and Core2D with 7.
So far what I've found and am currently trying to learn about is imagex and .wim files. I think what I'm trying to do, if it's possible, is create a single .wim image for each configuration, and have each system boot from this image every time. So to make changes or update the system, I would just have to work on one computer, image it, and copy that image to the other identical systems.
Things I need help with/don't know:
- Is it even possible to boot windows from a local read-only .wim image?
- each computer should have a unique network name, would that be possible using the same image (such as with windows deployment services [don't really know how that works or will be used at this point])?
- If I need a server to get this to work, i should be able to add a window 2003 or 2008 to that network, but it's still on 10/100 so i'd prefer not to boot from the network.
- as opposed to booting from the network, could I get the client to download a new .wim image over pxe (such as by manually selecting pxe boot from bios startup only to pull updated images) and then boot from the local drive?
Right now I've just finished downloading the windows AIK, so my current step is just creating a test .wim image.
This is well beyond the scope of my normal job description, but I'd really like to be able to get it working. I'm very new to windows server and deployment situations and most of what I know I've learned in the past two days, so any help or even links to read up on would be much appreciated!
Edit: is this even in the right section? I put it here because I had the integration with server 2003/2008 on my mind, but after reading it over I realize most of my questions are regarding local file access.
Last edited: