Posts made by m.fitzgerald

@wayne-workman Not sure why they are not available. This would be the only 3 or 4 PC’s grabbing an image. Also during the test to try and isolate the issue I was only doing one.

…Location Plugin restrictions can only apply to registered hosts that are assigned a location.

Correct, I understand that. This is not the issue. I am referring to NON registered

@wayne-workman said in How do I change to order of the Location ID’s?:

I want to point out that your entire problem is caused by not doing ‘a few extra key strokes’ to register the hosts and assign a location.

Initially we did not need to do this step. We plugged it and went ahead. My reason for asking is to understand what has changed and how to correct it. Also it requires less interaction. We are a two person department for close to 1,000 people and 800 devices. Every second we save is welcomed. Thus our desire to use FOG. We’ve cut turnaround time for broken PC’s down from 3hrs to 20 min.

@sebastian-roth It’s not a stupid question. Here is the reason we do not. 50% of the ghosting we do is on site after the PC has been deployed and registered in FOG at its proper location.

The other 50% we do is for PC’s at my office that have not been registered or are new PC’s. To make the process faster we simply boot into fog and choose deploy image. For some reason the PC will grab a storage node that is located at a different location from time to time. No real reason I can see on why it chooses what it does.

We can do it via registering first but it is a few extra key strokes and when we are doing 10 or so at a time it keeps it faster.

Opening new thread per @sebastian-roth instructions.

We currently have 5 nodes with one as the master. The problem is that if a PC has not been assigned to a node it will try and pull an image from the wrong node because the “Master” is listed as the number 3 choice.

Any idea how to change the order? I have tried deleting and readding but it seems to not matter.

Thanks in advance.

@sebastian-roth That solved the boot issue! Thanks. Now all is working as normal. Hard drives are re-sizing properly now. We have tested it on 4 machines.

Case Solved.

@sebastian-roth

D1.Fixed
:3

d1.min
label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 119716, type=7, bootable
/dev/sda2 : start= 1026048, size= 85513176, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

d1.orig
/dev/sda1 ntfs
/dev/sda2 ntfs

d1.part
label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 1024000, type=7, bootable
/dev/sda2 : start= 1026048, size= 973697024, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

@george1421
Yes it is 1709
Bootrec /rebuildBCD did the trick.
It is a UEFI with GPT and no bitlocker

I solved the above boot issue by doing the below from command prompt on the target PC.

Bootrec /rebuildbcd

Now the PC boots. Also the hard drive is the proper size. What I do not know is why the BCD showed unknow for Device as well as OSdevice. Once I ran /rebuildbcd the Device and OSdevice both now show the proper partition=c:

So it seems we have solved the Hard Drive issue and now have a new issue. Thoughts?

Below picture BCDedit is Before

I have captured a new image and now I think I may have a different issue or the same issue with a different result.

Now when i deploy the newly captured image onto a PC that would not resize I get the below picture. I have tried this new image on 3 PC’s and all three come back the same. I also get the same result on any of the old images. I am not sure if this is a resize issue or not.

For reference, we use FOG to deploy images already setup as we need. Meaning that we take a brand new unactivated PC and load our needed software onto the PC. Once done I select the host in FOG and request a capture. This is the same method we have done for the past 8 months or so and we used it routinely to “freshen” up PC’s. Only until i switched to a new server and reinstalled FOG with a fresh download did the re-size issue pop up.

@quazz Ok, I will do so now and report back

@quazz English (American, not proper English )

@sebastian-roth

d1.partitions

label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 1024000, type=7, bootable
/dev/sda2 : start= 1026048, size= 973697024, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

d1.original.fstypes

/dev/sda1 ntfs
/dev/sda2 ntfs

d1.minimum.partitions

label: dos
label-id: 0xae2e5b63
device: /dev/sda
unit: sectors

/dev/sda1 : start= 2048, size= 119716, type=7, bootable
/dev/sda2 : start= 1026048, size= 86818208, type=7
/dev/sda3 : start= 974723072, size= 2048000, type=27

d1.fixed_size_partitions

:3

@george1421
I updated to 1.5 and took my same machine that Ii was having the image size issue with and deployed the image again. Have the same resizing issue.

Should I recreate my master image now that I have switched to 1.5? Also I am not sure if it matters but i do not run sysprep prior to capturing an image. It is something i have never done.

@george1421 What the hell, I am a gambling man. Point me in the right direction!

@george1421

We use a multi site environment with one main site and 10 remote sites. If I were to switch to the Dev Branch I assume I would need to upgrade all servers to match, correct?

Fog Server 1.4.4

Looking for assistance with a new issue we had pop up.

We have been using FOG without issues until maybe 2 months ago. Now when we deploy a new image perhaps 60% of the time the Hard Drive does not resize. It keeps the imaged hard drive the same size as the image being pushed out and leaves any remaining space as unallocated. On the ones that do not resize properly we run a powershell script to resize the hard drive after install. This puts everything back to normal.

The only change we made from when it worked fine to now is a change to a new server and a fresh download of FOG from the website.

Any thoughts?

Problem solved.

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

Was the part I needed. Thanks!

@wayne-workman Exactly what I needed. Thanks. I couldn’t find that anywhere!

@george1421 Simply, I want to install the client app on 800+ computers as below.

Site “A” needs to point to fogserver1,
Site “B” needs to point to fogserver2,
Site “C” needs fogserver3.

When i install the packaged MSI from the fogserver the server name is wrong since it is simply “FOGSERVER” I need the flexibility to change it to what each site needs so it hits the local server and not the server at the primary site, and i need to do it via an MSI file so I can send it to 800 PC.

Since all sites share the same DNS server I can’t simply create an “A” record.

Hope that helps.

@george1421 Well, perhaps i don’t if you have a way to differentiate a local fog server for each site. Since we connect VIA VPN at 50MB fiber to each location I do not want the off site (from main location) pulling down such large files via the VPN. The time it takes to download the 30-60GB image is too long. It is almost faster to drive to site and load while there.

Speed considerations are the only reason i want to separate.

@wayne-workman Each location does share the same DNS server, but we connect via VPN to each site and and don’t want every site pulling or pushing 60gb files as needed. Local is much better for our environment.

Additionally I know I can deploy via GPO but I already have PDQ for other applications and I use it quite frequently already.