How do I change to order of the Location ID's?



  • 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.

    0_1514308824409_536001023_20171226_121154.jpg

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

    Thanks in advance.


  • Developer

    @m-fitzgerald Can we mark this solved?

    @JGallo Interesting suggestion…



  • May I suggest the following:

    https://forums.fogproject.org/topic/9851/custom-full-host-registration-menu-for-1-4-0-rc2-and-later

    You may edit the registration process by eliminating questions you don’t want to deal with. Hence cutting the registration process depending on how many questions you eliminate. What I have done is removed unnecessary questions like product key, group, etc so that only three important questions are asked. Name of host, image ID, location, and then image now. If you have groups, you could just use the web ui to group them together. Mind you, this is only a suggestion to your scenario as my environment has several storage nodes and master nodes within those storage nodes and I replicate images across domains. Pretty cool in the end that FOG is capable of this.



  • @m-fitzgerald said in How do I change to order of the Location ID’s?:

    Initially we did not need to do this step.

    This is how the location plugin has always worked. If a host is not registered, FOG simply chooses whatever node that has the needed image and also has empty slots, location configuration is not taken into account because the unknown host has no location information.



  • @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.



  • @m-fitzgerald said in How do I change to order of the Location ID’s?:

    For some reason the PC will grab a storage node that is located at a different location from time to time.

    Because they are not registered, therefore are not assigned a location. Because of that, FOG uses whatever node that has empty slots. Location Plugin restrictions can only apply to registered hosts that are assigned a location.

    We can do it via registering first but it is a few extra key strokes

    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.

    The overall issue I see here (not the location problem) is that you’re trying to use advanced imaging features that FOG has with a cloning mindset. FOG is not Ghost. FOG is an imaging solution, where imaging means intelligently applying an image and then configuring it. Ghost is a cloning solution, where it un-intelligently applies an image and does no configuration. Most of FOG’s intelligent imaging features require hosts to be registered, one of those intelligent imaging features is the use of locations.



  • @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.



  • I’ve wrote a tool to renumber snapinIDs and imageIDs, location IDs is really just a couple tweaks to do. Do you want to take a shot at it? Just be sure to backup your fog database before mucking with things and all will be fine. You’d backup like this: Web GUI -> FOG Configuration -> Configuration Save -> Export Database -> Export


  • Developer

    @m-fitzgerald Thanks for opening a new one on this.

    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

    But why don’t you assign the correct location as being asked when registering? Sorry, this might sound like a stupid question but I don’t get where exactly you are headed with this.


 

429
Online

41.5k
Users

12.0k
Topics

113.4k
Posts