@Rama This thread is fairly old, and the OP is probably not going to respond. Can you please create a new thread with all the details, fog version, how you are doing it, etc.

@Joe-Schmitt said in Hostname is correct:

Just try disabling it, and re-imaging.

Works !

@Wayne-Workman
Yeah i know my setup is not a regular configuration, but now it works with nfs server on windows , in upload / download. As you know there are more chances to encounter a problem in upload… ^^

@danilopinotti So that worked?

@danilopinotti Correct.

@Tom-Elliott Wanted to clarify what @Scott-Adams was saying for future readers.

If you have a host that is pre-existing in FOG, and you then set AD defaults, those don’t automatically get applied to already-existing hosts. If you want to re-set or re-assign or update AD settings on pre-existing hosts enmass, use groups to do it.

@danilopinotti So the admin network and the academic network are on two different broadcast domains, and maybe even further separated logically via Vlans.

Then you just need a FOG server with two network interfaces (and connect each one to each network). You’d have two storage groups, and in each of those, one master node each, pointing to the exact same directory, but a different interface and IP for each (for the two network interfaces). I think it could work.

Or, just totally separate out the admin images and academic images. Have a storage group for each, and put each one on it’s appropriate interface and IP, and give them each a separate folder.

But Tom is probably right, the location plugin would be far more simple - just have two fog servers, one just a storage node for academic. Set each up as a location, and maybe even give each their own storage group, and make each the master of their group.

Lots of options.

But - the thing that I’m most concerned with is keeping the domain information straight. You’ll really, really need to pay attention to that - or you might find all of your computers joined to one or the other domains… and that wouldn’t be good at all. So there’s a whole lot of possibility for a really large failure with this setup.

@Sebastian-Roth Thank you.

Added checking code to remove any package that can no longer be found.

@danilopinotti said:

in the installation, i’ve set the Fog to use the eth1 interface, and even then, the default storage was set to eth0.

Tom got that fixed in the trunk.

@Wayne-Workman
Yes, after open all ports, it works

Found, confirmed, and fixed plus a little.

Snapin associations weren’t being deleted for whatever reason, so I’ve added code to ensure it will do so now.

To fix the systems that currently believe it’s already broken, we do the same thing.

I check the associations, check the valid ID’s, and delete associations that are no longer valid when compared to the two primary tables.

@danilopinotti Is this still an issue or can we make this solved? Have you tried upgrading to the very latest version, re-upload and deploy again?

Now works, but Windows not boot more
A pointer appears blinking in the upper left corner of the screen…

Please update.

I believe this is now resolved.

Sorry it was the way it was trying to store the data.

@danilopinotti If you can get in touch with me via Chat, I’d be happy to explain and even help out if we could schedule it.

Beyond that, follow the instructions below. Just test it for each revision. When you find one that fails, try the one between the failed version and the last working version you tried. Keep doing that until you find which version it is.

I use FOG 4469

I need to activate machines in the following situations:
Multiple machines with the same key
Multiple machines with different keys
Activate computers after imaging for that in the future, I can replace them.

@Scott-B just about every printer in the building is a different model. of which we have about 100. Some are USB, some network.

I manage the network ones with Active Directory without issue - it’s just this one printer being stupid. It needs replaced. It doesn’t even have drivers for Windows 7, I finagled Windows Vista drivers onto Windows 7 as a local TCP/IP installation before. It’s just impossible to deploy with Active Directory - everything I’ve tried has failed - and I’ve tried a lot.

Fog was my last resort.

But, here in the future, if it proves to be reliable and I think it will be, I want to use FOG for printer management because it’ll lighten the load on our DCs.

I formatted the machine again, only this time I created the partitions before sending install direct. In this way it worked.

I have created a plugin to allow people to change the task types as they see fit.

I did this for two reasons. First, I don’t find the current states that hard to follow. When it comes to tasks the POV is always from the client/host. So download means the client is pulling from the server and upload means to push to the server. The hosts, after all, are the items that get tasked. I have had this discussion multiple times in the past and I still stand strong that they’re fine the way they are. That said the plugin allows the admins to use whatever terminology they deem necessary.

The second reason is to allow the admins to make the tasks as they see fit. For example, make a currently advanced task non advanced so it displays in the main task list. Or adjust the tasks to be shown on only group or host where they are currently shown on both. Ultimately this plugin allows the admins to create/edit the tasks as they see fit.