Posts made by Jim Graczyk

Regarding Bug Reporting - do you want a separate Topic for each thing we find or would you rather we compile a list and submit it as a single Topic? Just for future reference…

Jim

@Tom-Elliott

We’ll update at lunch time. We just ran the update at about 9am Eastern and we need to get work done on the project. We’re good as long as we don’t shut down storage nodes…

Do want to point out that even with all nodes up, the time after one clicks on a snapin to edit it and the time after clicking on the Storage icon are much longer than other actions and seems unrelated to the amount of data being pulled (heck our database dump was 500K so it’s certainly all in RAM on the server).

Jim

Server

• FOG Version: 1.5.0 RC3 today’s update
• OS: Cent)S 7

Description

After editing a Snapin and hitting Update, I received the following text in my browser (Chrome):

{“msg”:“Snapin updated!”,“title”:“Snapin Update Success”}

This occurred w/o the expected pop-up message we’re seeing elsewhere in this WebUI update.

Jim

Sorry - I misspoke -

It seems the problem is with the entire UI, not any particular action. Having a storage node off appears to negatively impact the entire WebUI. We’re seeing delays of 2 minutes, then some brief time of regular responsiveness, then 2 minute delays, across the WebUI.

Specifically, hit storage icon, waited 2 minutes, then had enough regular responsiveness to click hosts, then groups, then Snapins. when I click on a particular snapin, it took another 2 minutes to come up.

Restarting the down storage node returns the WebUI to normal responsiveness.

Jim

Server

• FOG Version:1.5.0 RC3, today’s working branch on all FOG servers
• OS: CEntOS 7

Description

I found that when a storage node is configured and not working, the webUI Storage Icon takes a long time to update. This delay occurs when you add a new storage node that isn’t connected or if you shut down a storage node that was previously working fine.

I never connected the new storage node since it was just a test, but the problem more or less goes away when you restart all defined storage nodes. I say more or less because the time to update the screen after clicking the Storage Icon can be 15+ seconds when the nodes are up and working with just 2 storage nodes. If the code in the WebUI is serially contacting each storage node, the normal update time could be lengthy if you have a dozen storage nodes defined (which we will).

Jim

@Tom-Elliott Update Worked! Location plugin was installed when the update was made. Was able to disassociate several images from several storage groups.

We can consider this resolved.

Thanks.
Jim

@Tom-Elliott
That would be much better than having no indication which snapins are assigned. Some indication in the snapin name (like an asterisk or such at the end of the Snapin name) would be something I could live with.

Jim

@Tom-Elliott

Yes, I understand what you’re saying but I use Deploy a single snapin much more frequently than deploy all snapins.

Actually, the only reason I have to deploy all snapins would be with an image. It’s very rarely used alone. Maybe for some debugging and it’s good to have it in the lab.

I believe this Single Snapin change will be liked by a few but hated by a larger number in the long run - and it’s likely to take some time for mistakes in the field to lead folks to dislike the change.

I’ve been doing deployments and helpdesks back to NT 3.51 in some very large companies, but it’s still just one man’s opinion.

You’re welcome to consider this issue closed.

Jim

In my opinion, this is a BAD idea.

We have different snapins for different OSs and we have to manage many types of images at any given time. We have a list a of snapins a mile long - many of which cannot / should not run on some images. Someday, Access Control will be implemented inside FOG, but until then, we manage FOG use on an honor system. Some people have the task to decide what snapins go on what machines, while others have the job of deploying snapins.

FOG’s ability to image and then apply snapins is a good feature, but in my life, we’re normally deploying snapins more frequently on an as-needed basis to repair an existing snapin install or to send software to a PC that didn’t need it until sometime long after imaging. We’re also always making new snapins for maintenance and to meet the users’ needs and these are always deployed one at a time. In point of fact, we create images that have the majority of the snapins already installed (like MS Office) to save on the deployment time.

In my opinion, allowing single snapin delivery of any snapin will lead to a lot more extra work in the form of re-imaging to undo mistakes being made.

I strongly suggest that you consider returning this feature to how it’s been. The inconvenience of having to select a snapin for a PC prior to deploying that snapin actually saves time we’ll have to spend due to mistakes and acts as a safeguard against time-consuming mistakes.

Jim

@Tom-Elliott

Sebastian, I know we delete records when we were looking at the install here over the weekend. Would any of the deletes we did apply to what Tom’s talking about?

Jim

Server

• FOG Version: 1.5.0-RC3
• OS: CEntOS 7

Client

• Service Version: latest
• OS: Windows 10 x64 Pro running Chrome Browser

Description

When selecting Host/Basic Task/Advanced/Deploy a Single Snapin the pull down list contains all Snapin defined in FOG, not just those assigned to the host in question.

Jim

Tom has a good point here. I’ve struggled with launching powershell from the FOG Service with the correct privilege level to prevent UAC pop ups you never see. Disabling UAC on a PC and retrying the snapin will can be a good testing step. Windows 7 and Windows 10 treat UAC differently, or so it seems. To get around UAC in Win7. Seach for elevate.cmd and elevate.vbs that came out with Server 2008/Vista. I’ve found that this can successfully elevate a PS script in Win7. I’m still working on Win10.

if you’re actually getting powershell to start your script, you can also pipe the output to a file using the out-file cmdlet:

powershell.exe -Executionpolicy Bypass -noprofile -file myscript.ps1 | out-file full [full path to some text file]

Jim

@Tom-Elliott Location Plugin is uninstalled but still cannot disassociate an image from a storage group.

Jim

@Tom-Elliott

Doing so now. And FYI - I had uninstalled the Locations Plugin and reinstalled it this morning - before I ran into problems. I was AFK some and will be again in 45 mins. I hope Sebastian was able to record what he and I did today over WebEx. I don’t know that I can provide sufficient detail to assist you. I haven’t seen any posts from him since we concluded the WebEx.

One thing I did want to tell :

I have a FOG and 2 Storage Node Servers. I have 3 Locations defined and 3 storage groups with one FOG server in each site and storage group. If I shut down one of my Storage Nodes or Make a new storage node, when I click on the storage icon in the UI, the UI goes unresponsive for about 5 mintues. Start the node back up and it the Storage icon response time is about 10 seconds.

Once I have locations plugin uninstalled, I’ll attempt to disassociate an image from a storage node and report back.

Jim

@Jim-Graczyk

My next test was to add new objects to the existing FOG configuration to see if I could get the results others are getting with object created in this version of FOG.

I did the following:

• Created a new location
• Created a new storage group
• Created a new Host (fake MAC)
• Created a new storage node (non-existant IP address). I think I put the new storage node in the new storage groups, but not sure due to problem described next.

When I hit add on the storage node, I got the storage node added, I got the message Storage Node Added, but then the web UI failed to respond from that point on. The server was fine and not showing a lot of load, but the UI just sat there (for several minutes). I rebooted the server and was able to logon to FOG. the dashboard came up - minus the storage node graphic - and then failed to respond.

I have disconnected the server from the network, rebooted it and attempted to connect to the fog website via localhost, but I get no response. FOG wed UI may not be bound to the local host IP.

I’m at a loss. It’s Sunday and I’m off tomorrow, but have people who need FOG up and working tomorrow morning.

My only choice may be to restore my FOG server 1.4.2 - as it was configured and working before I attempted to upgrade to 1.4.4 and ended up with 1.5.0 RC2 via my system backups and leave it there for now. If I don’t hear from anyone on this, I’ll assume I need to uninstall FOG from my storage nodes and reinstall 1.4.2.

Jim

@Sebastian-Roth

Sebastian,

Tracking message sequence in this website isn’t straight forward. I didn’t see this message before I posted my last with all the screenshots, nor did I see it before I attempted to add test items to my system and see if I could at least manage new items (Host, Storage Node, Storage Group and Location).

Adding these items seems to have completely messed up my installation of FOG. Please see my message to Tom for details.

Thanks,
Jim

@Tom-Elliott
Here are my Locations:

Note that the SAL2 Location has storage group 101Space.

Here are my storage groups:

Note that SAL2FOGL1 is the only storage node at the SAL2 location and therefore primary storage node in the 101Space storage group.
Here’s an image:

This image is stored in these Storage Groups:

Here, I attempt to remove the image from the storage group - I select the storage group and click Remove:

Next, I list all images:

Select the same image as before:

Select the Storage Group Tab:

The supposedly deleted Storage Group is still listed.

Am I seeing something different from what you’re seeing? I’m running on CEntOS 7. Could that be an issue?

Jim

@Sebastian-Roth

By Delete I only meant disassociate the image with the storage group. I was only explaining what I was doing that caused me to discover that I couldn’t delete the association of an image with a storage group. I had what appears to be a bad replica of an image at one site. Since I’m using the Locations plugin, there is one storage group defined for each location and there is one storage node in each storage group.

To remedy the bad replica, I tried to disassociate the Image from the storage node/group at the site, delete the back copy, then re-associate the image with the storage node/group so the Image Replicator would re-copy the image to the site. While doing this, I discovered that I could not alter what storage groups were associated with an image.

Jim

@Tom-Elliott
Tom,

I mean all of that.

Select a squarish checkbox (not the radio buttons), checking a storage group from which to remove the image. I hit Remove (big red button) a popup comes up and says Image updated. If I wait the popup goes away or I can hit X and close it. In both cases the display doesn’t change. I log out, log in and select the same image, click storage group tab - all 3 storage groups remain for the image. I’ve tried F5 to refresh the browser - same thing - 3 Storage Groups listed. I shuffled around the other tabs, same. Was using Chrome, logged in with Edge (hate it) and the image is in all 3 storage groups.

Jim

@Tom-Elliott

Looks like the reports now work. Thanks.

I do suggest that the user tracking report would be much more useful if it listed all record chronologically and showed the timestamp field. The summary report of who ever login in on a machine or what machine a user ever logged into is less valuable than the detailed report that one could filter at the headers based on any of the fields. This makes the snapin log work, and that would work here as well - imho.

Thanks a bunch… please make this one as Solved.

Jim