Hello,

thank you for your help : In fact, I deleted the client and update … it’s now ok !

It could very well be a compatibility thing.

Perhaps the motherboards are newer and have UEFI turned on? Or Secure Boot?

Make sure DHCP is running on your FOG server still. Make sure TFTP is running.

And, grab that Dell that worked before and verify your FOG box still works.

It won’t use any rearms at all unless you actually run sysprep. If you do run sysprep and you don’t want it to rearm, just include Skiprearm set to 1 in your unattend file.

Here’s a bit of my unattend file so you can see where the SkipRearm bit should be:

<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:sc.... <settings pass="generalize"> <component name="Microsoft-Windows-Security-SPP" ..... <SkipRearm>1</SkipRearm> </component> </settings>

As for not being activated - I found it annoying and activated in the end, since you have something like 3 rearms you can use. But I think it at least affects Windows updates so if you wanted to include those on your image, then activate once if you can.

I apologize, the search feature on our (new) forum has been temporarily disabled. It sometimes crashes the site…

anyways…

Can you give these threads a quick once-through?

https://forums.fogproject.org/topic/4985/uefi-secure-boot-fixes-abound-but-is-there-a-solution
https://forums.fogproject.org/topic/4981/surface-pro-3-imaging

For this endeavor, if you’re not using Trunk, I’d recommend getting it.
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
https://wiki.fogproject.org/wiki/index.php/SVN

Thank you all so much for your responses. They were both timely and very helpful. I am very close to implementation of this system (only have a OS/2 Warp on HPFS hurdle to jump) and I’ll be ready to pitch the idea to the server team. I’ll be active in the forums on my findings going down this road (contribute) in an effort to pay you all back for you help.

I fully understand that documentation is a huge time sink! I hope I can help.

I renabled fog on the client and deleted everything from the master. It did not remove the tasks even after a service restart.

I’m creating a batch file with this command:
schtasks /delete /tn fog\20@0@s /F
This deletes the task scheduler items. The 20@0@s is how the name of the tasks that are created show up.

Thanks Wayne. I’ll start to build a FOG 1.2 and see how things turn out. Thank you for your advise.

I’ll walk you through upgrading, if you haven’t torn out the installation yet…

[quote=“davido38, post: 46961, member: 29185”]I use DPINSTALL but not in the sysprep. I use it at the end of the setupcomplete. It works very well for now.[/quote]

Hi,

If you manually update a device driver after installation with the DP have you some problems ?

Regards,
Ch3i.

[quote=“Wayne Workman, post: 46472, member: 28155”]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.[/quote]

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!

I’ve left the PXE menu activated to register everything to begin with during my deploy period.
But for my use/production period, I will have it as NO MENU.

Seems like its just not the right tool for the job the main difficulty’s that come to mind is where will images be if you use an external drive how to insure it mounts correctly each time you switch hardware and usb port you would be restricted to quick image no way to maintain a database on read only media. and for a one time image there are already solid tools that don’t require a second machine to act as a server like the aforementioned clonezilla. Not to say that a more simplified install and setup might not make sense to develop. More like a fog for dummies that would have you boot off a cd or removable media image and is preconfigured for dhcp ect using the first available hard drive for images and data. sort of a lowest common denominator fog and os combo to minimize possible issues for the end user.

Disable pxe in your bios option, and put the HDD on first place in the boot order

Hello, new computer assistant working with open source, I saw myself assign the FOG project.

The problem is that my company uses to install CUPS printers.

For any machine windows we use the Add Printer wizard windows
Printer and fax ==> Add / Remove Printer ==> adding a network and the printer is typed syntax ==>
[url]http://cups.domaine.com:631/printers/nom_de_limprimante[/url]

I understand that this is a protocol ipp / htpp (I know not all cups)

how to add this printer in FOG for it unfolds on Windows?
When I run FOG customer I see my client FOG that update me my printers ==> Printers XXXX installed, In the logs nothing special but no printers on the post …

If somebody can give me would be cool thank you ca info

Ps for the driver is a second plane because I know Cups with the ability to “push” the drivers during installation (FOG also from what I understand) this time I would like to least have a windows prompt asking me to install the driver.

Thank you for your information and keep your actions! I just stumbled into the world of open source and it is impressive: p

thank you,

I’ve got FOG 1.2.

Sorry for my mistakes 😛

thanks for the info guys. I ended up adding a command to setupcomplete.cmd and that seems to be working.
tzutil /s “applicable time zone”

Thanks guy for help.

We don’t really use fog like many of you.

We are refurbisher, we buy lot of used professional stuff and sell to end customer with low cost.

When i came in the company, they used a old Ghost server and we test fog, loved and adopted !

I am not really good in english, and sometimes, it’s hard to follow technicals threads, but i learn lot of thing on linux.

You are all devoted to this project, and it’s nice to be able to discuss and improve the project with you.

[quote=“Junkhacker, post: 43983, member: 21583”]btw, the domain\user issue is changed in the dev version of the code. in the current dev version of the code, the user field is checked for a \ or @. if either of those exist, the field is sent as is. if not, the domain is a added as domain\user.[/quote]

Yes, Tom told me about that, and what you describe seems exactly the right behaviour.

It is solved.
Thanks.

Since I am still kind of new to FOG I am not absolutely sure about FOG 0.32 but I suppose there is not too much of a difference when it comes to MBR…

FOG (1.2.0 an newer) does save the MBR from the uploading client at least with image type mps (single disk multiple partition) and mpa (all disks multiple partitions)! bcd(edit) has nothing to do with MBR! Those informations are saved in the first (100MB) partition of your disk, not in the MBR.

As FOG 0.32 is not under development I’d suggest you try setting up a test server with FOG 1.2.0 or even better current SVN version. If your issues still persist we are happy to jump in and fix things for you!