[SIZE=2][COLOR=#000000]Hi all :)[/COLOR][/SIZE]
[SIZE=2][COLOR=#000000][/COLOR][/SIZE]
[SIZE=2][COLOR=#000000]Might just be me being daft but have encountered a minor issue. When I select a group to join AD after imaging task completes nothing happens, All works fine if I flag a single workstation though. What I have noticed is when I check the Join Domain after Image task and hit update the automatically populated values that are pulled in from AD Default settings vanish and check box is cleared.[/COLOR][/SIZE]
[SIZE=2][COLOR=#000000][/COLOR][/SIZE]
[SIZE=2][COLOR=#000000]Like I say all works fine when this option is chosen for a single desktop, everything works as it should from hostname change to stashing the machine in my chosen OU.[/COLOR][/SIZE]
[SIZE=2][COLOR=#000000][/COLOR][/SIZE]
[SIZE=2][COLOR=#000000]Any help as always is greatly appreciated, it could well be that I have looked at it so long I am missing something silly :)[/COLOR][/SIZE]
[SIZE=2][COLOR=#000000][/COLOR][/SIZE]
[SIZE=2][COLOR=#000000]Cheers[/COLOR][/SIZE]

[SIZE=2][COLOR=#000000]Robbie[/COLOR][/SIZE]
[LEFT] [/LEFT]

I can also confirm :
Optiplex 790, Latitude E5420 and Latitude E5330, will check what kernel I am running but this is on 1.1.0 and had no issues.

EDIT just noticed a typo in my post its the Latitude E5530, sorry about that

Everything working perfectly, Thanks Tom.

Like the additional group association option too

Cheers
Robbie

Hi Tom,

That’s great thank you, have just updated will let you know how it goes

Many thanks
Robbie

Thanks Tom,

I get inventory, everything else is working perfectly other than the above

Sorry forgot to add, this happens with any machine that gets registered, I am currently running the latest kernel on 1.0.1, again it doesn’t fail to register the hosts, it just sits there on the “Attempting to register” screen even though the host has been successfully registered.

Thanks again
Robbie

Hi Tom,

Sorry for not being 100% clear. Basically what is happening is when PXE booting to the FOG menu I can use quick register to register the host, the process runs and the host actually registers with the FOG server but instead of getting the usual “Attempting to Register…DONE” I am just getting “Attempting to Register Host…” and it just stays there on the black screen. For every second it sits on the black screen the value in FOG_QUICKREG_SYS_NUMBER goes up until I manually restart the machine so that when I come to register a new host instead of it being for instance WORK-LAPTOP-002 it would be WORK-LAPTOP-009 resulting in the numbering sequence being all over the place. When doing a small group of machines I just go in and change the number to the next in the sequence but I have a roll out of 400+ machines coming up shortly and was just wondering if it was something that needed changing in a script somewhere so that after a machine is registered it acknowledges it and stops the FOG_QUICKREG_SYS_NUMBER value increasing so that when I next come to register a host the value only increments by 1.

I am using fog 1.0.1 but never had this issue with 0.32, I hope this makes a little more sense

Cheers
Robbie

Any help would be most appreciated

Thanks
Robbie

Hi all,

I have an odd problem that is probably very easy to resolve, when I Quick Register a new machine it adds the inventory and registers the host with the FOG server but just sits there on the black screen sayin attempting to register. As I say the machine registers and reboots normally however in FOG setting the FOG_QUICKREG_SYS_NUMBER has gone up considerably, It looks like while it was “attempting to register” after the initial host registration it didn’t stop ticking over.

Is there anyway to get around this at all?

Kind Regards
Robbie

Hi All,

Have just built a new FOG 1.0.1 server and additional storage node. I have added the node and attempted to check it by tailing the fog replication log but it doesn’t appear to have been generated, also when I go to the home page on the dashboard and select the storage node in the disk info I get a message saying failed to connect in the disk info box. I have added the node as a slave in the default storage group and as a master in a new storage group called desktop but this has made no difference however when I add an image with the location pointing to the storage node I can actually image to it. I also have a 0.32 installation and have never come across this, any ideas / help would be greatly appreciated

Kind Regards
Robbie