Screen Resolution



  • I have a question regarding the screen resolution changer feature on FOG, I set the resolution for all hosts to 1280x1024 in the fog Web UI and when the computers boot up some are still on 800x600 or 1024x768 usually most of the computers boot up with the max res after imaging but there are some that go wonky and i dont want to have to go around manually changing resolutions. if you need the fog log out of a computer i can get one



  • @Wayne Workman, post: 46472, member: 28155 said:

    FOG does not support downgrading, you’ll just break things worse if you attempt to downgrade.

    I personally use snapshots in Hyper-V. I take a snapshot before each update, and I keep my last two snapshots for a long while till I know things are solid. I’ve not had to revert to an earlier snapshot though. Although I know that most don’t have resources to do this, and maybe not the permission to manage windows servers.

    But, because you’re so concerned with safety and reliability, I recommend the following:

    Instead of “upgrading”, I’d recommend exporting your DB (using the configuration save feature inside FOG Configuration) and exporting your images also. Turn off your old FOG server and set it aside in a safe spot, and build a new 1.2.0 build. Import your configuration and images. Verify all is well with this build, verify that everything works. Then upgrade that.

    This will provide you with a way to go back if things don’t go well. It’s not the fastest point from A to B, but it will give you the safety net you’re looking for. Also, I’m not attempting to foreshadow failure or anything. If you run into issues with the Newly built system that you upgrade, just come to the forums; we will help. Tom smashes bugs really fast, and there are a lot of people here that are great with troubleshooting.

    I was thinking of doing something like that…i probably wont even take my current fog server down ill just export everything and setup a duplicate on the test lan that only the admins here have access to…and yes i have full access to all the servers so nothing is stopping me from testing everything and i do have an OLD 1U Server just sitting in one of the racks so that well work Thanks!


  • Senior Developer

    Or, you can use clonezilla to make a local ‘image’ of your FOG server depending on how big it is. It really all depends how you want to back up your FOG server, but you should [B]never[/B] upgrade your production server without some way of reverting it.


  • Moderator

    @Ziricom, post: 46469, member: 26229 said:

    Ok…so before i upgrade to the Trunk Version…is there any system breaking bugs i need to know about? and can i revert to Fog 1.2.0 by re running the fog 1.2.0 installer if i want to?

    FOG does not support downgrading, you’ll just break things worse if you attempt to downgrade.

    I personally use snapshots in Hyper-V. I take a snapshot before each update, and I keep my last two snapshots for a long while till I know things are solid. I’ve not had to revert to an earlier snapshot though. Although I know that most don’t have resources to do this, and maybe not the permission to manage windows servers.

    But, because you’re so concerned with safety and reliability, I recommend the following:

    Instead of “upgrading”, I’d recommend exporting your DB (using the configuration save feature inside FOG Configuration) and exporting your images also. Turn off your old FOG server and set it aside in a safe spot, and build a new 1.2.0 build. Import your configuration and images. Verify all is well with this build, verify that everything works. Then upgrade that.

    This will provide you with a way to go back if things don’t go well. It’s not the fastest point from A to B, but it will give you the safety net you’re looking for. Also, I’m not attempting to foreshadow failure or anything. If you run into issues with the Newly built system that you upgrade, just come to the forums; we will help. Tom smashes bugs really fast, and there are a lot of people here that are great with troubleshooting.



  • Ok…so before i upgrade to the Trunk Version…is there any system breaking bugs i need to know about? and can i revert to Fog 1.2.0 by re running the fog 1.2.0 installer if i want to?


  • Senior Developer

    No. The new beta client will only work with the development version. Much has changed ‘underneath’ FOG.


  • Moderator

    There’s been tons of changes made to the web-gui & DB for the new client.

    I’d strongly recommend[B] against[/B] sticking the new client into the old 1.2.0. I doubt it’d even work.

    edit: I left out against… I recommend [B]AGAINST[/B].



  • http://fogproject.org/wiki/index.php/Upgrade_to_trunk

    I use the developmental revisions at work, without them FOG would not work for my environment.[/quote]

    Ill just use the developmental version…screw it, if something breaks and i gotta spend hours to fix it well then…more money for me xD one question. Is it not possible to use the developmental version of the fog client with the normal version and have this work? if so ill just setup a fog server ina vm and get that client from it


  • Moderator

    It’s only available in the developmental versions.

    Feel free to try, although I’d recommend making a snapshot/total backup of your fog machine prior, or just turn it off and build a new one for now.

    http://fogproject.org/wiki/index.php/Upgrade_to_trunk

    I use the developmental revisions at work, without them FOG would not work for my environment.



  • Using the client that came with FOG 1.2.0 So where do i get the working client??


  • Senior Developer

    Are you using the Old or new client? If it’s the “Legacy” (the one that came native with 1.2.0 and prior) this will not work.


Log in to reply
 

364
Online

38724
Users

10553
Topics

99875
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.