Please Add an Option to Change the Default Page After Logon
-
I’m constantly logging into FOG from all over the place. Every time I log in, I have to wait many seconds and sometimes minutes before the Dashboard is displayed. Often, I just need to deploy a Host or single Snapin. I’m not overly concerned with the overall operation of FOG EVERY time I log in. For those of us with many locations, strung together with less-than-robust connections, the polling of the storage nodes (sometime many on fast connections, more often less than 10 over slow connections), delays the display of the Dashboard excessively.
Please consider adding to the FOG Configuration area a variable with a pull-down where a FOG admin can select any one of the large Icons on the top menu as the page to display after the user logs in. This parameter for be set for the entire web site and not for the user. We already have control of whether the top level pages show a list or a search dialog, so we’ll have great control of the responsiveness of the UI.
Thanks,
Jim
-
I set an Access Control rule to block access to the home node. It did take the icon away, but still took the user to that page at login.
-
Thanks. I haven’t had the need for the Access Control Plugin. I supposed it’s time. Thanks. I still believe it should be an option. The Dashboard is a good page, but it’s not the most efficient thing when you want to get on with FOG tasks.
Jim
-
@avaryan said in Please Add an Option to Change the Default Page After Logon:
I set an Access Control rule to block access to the home node. It did take the icon away, but still took the user to that page at login.
This is humorous I have to ping @Fernando-Gietz about this one.
-
Ping timeout 604800 seconds
Block the access to the homepage is not a good idea XD The behavour would be unstable.
By default, when you log on, FOG redirect to the home page, then if you block the access, the home page and the icon should not be drawn. -
@Jim-Graczyk All pages rely on “index.php”. The Default if node is not in the query string, or if node=home will direct to the dashboard. This is intentional as most people this shouldn’t impact too much. That said, this shouldn’t be a hard request to incorporate, but if you’re blocking the dashboard as being view-able, where should we redirect if a choice hasn’t been made?