Posts made by NT_Tech

Since upgrading to version 3359 only about 40% of my machines image successfully. I am all Dell Optiplex 780s and we have had 100% imaged prior to the upgrade. The "broken"ones boot to a blinking cursor and nothing else. Prior to this we were on 3273 with no issues. 60% failure is a pretty bad rate.

When searching for a host in the Host Management tab, the option at the bottom always gave the ability to add found hosts to a new or existing group. That option is now only there when listing all hosts but not on a search. Could this please be added back?

[url=“/_imported_xf_attachments/1/1959_all hosts list.jpg?:”]all hosts list.jpg[/url][url=“/_imported_xf_attachments/1/1960_FOG no Group Add.jpg?:”]FOG no Group Add.jpg[/url]

I am working now, except it now doesn’t seem to finish pinging every host when I do a search. I usually add hosts to a group by searching for part of the name, but it never seems to finish resolving the search if there are any more than a couple with the same name. When I turn off [I]FOG_HOST_LOOKUP[/I] it resolves the list quickly but no longer gives me the option to add hosts to a new or existing group like it used to. FYI, it does still show at the bottom of the all hosts list, but I never used to have to filter manually through 700 hosts to make a group. Previously I just put the search in the filter at the top and made groups easily and quickly.

I just realized this is really a new thread and have added it as such.

[url=“/_imported_xf_attachments/1/1957_FOG no Group Add.jpg?:”]FOG no Group Add.jpg[/url][url=“/_imported_xf_attachments/1/1958_all hosts list.jpg?:”]all hosts list.jpg[/url]

It was an error code 2, which I found a post by Tim E. that said it was something with the AD settings. I had my OU as C-Images instead of C-Imaged (should have taken a typing class in 1985 when I was in high school) and that might not have happened.

Logs are our friends…Logs are our friends…Logs are our friends…Logs are our friends…Logs are our friends…Ummmmmmm

Thanks, after going through the log we found the error code and rechecked the AD settings. The OU container was misspelled! AGH.

We are joining now and are upgrading to 3352 now to test it and hopefully stay there for a while.

I did try that…FOGCrypt came up with the same export (I still had the original file) as expected and I did delete all the fields and refill them in. I also checked the account as well, so those do not appear to be the issue. I am currently resending an image to a new host with 3123 to see if I am working with the old SVN before taking a new snapshot and trying 3352…4th revision today. I think the developers are working something.

FYI 3123 worked for me for a long time and I finally figured out how to get back to it.

Just click download snapshot from here.

[url]http://sourceforge.net/p/freeghost/code/3123/tree/trunk/[/url]

All releases are here and you can download the one you want…which is what I have been looking for!

[url]http://sourceforge.net/p/freeghost/activity/?page=0&limit=100#554786305fcbc9492ea58278[/url]

I just reverted back to 3273 to see if it will work. I found the checkbox but it is uncheck be default in this version…is it checked or unchecked in the newest trunk? That may have been my issue. I am trying to get a version to work at this point that IS svn since most of my images are in the new format and aren’t compatible with 1.2.

I am reverting to a snapshot on the VM to try and find a workable version again, unfortunately I have not kept all my svn versions that did work. Is there an archive somewhere to get old trunk releases? There should be a “most stable” trunk release site…I am hoping I just haven’t found it.

Thanks

Nope. Upgraded today to current SVN. The rename works but the rejoin does not. I installed the new client to see if that would fix it but that neither renames or rejoins the host to the AD.

Maybe I am missing something. I have the Active Directory settings setup exactly like I did before (I screenshot and copy the password to notepad) and still nothing.

Thanks!

We recently had issues with our single partition Windows 7 Images not expanding, about 30% weren’t expanding. We were already on SVN release so we upgraded to the recent 3333 release. As soon as we did, no host showed that it was registered with the FOG server. We made sure the hosts were registered on the server, but still no host showed registered on the FOG boot.

We reinstalled Ubuntu and FOG and went back to 1.2, only to find that the images were changed with the SVN releases and most of our images don’t work with the original 1.2.

So, we tried 3336 and the hosts now show registered on boot, but when we imaged they hostname changer and AD Joining part didn’t work, so we again went back to 1.2 (luckily I had a VM snapshot this time.)

I want to get back on the SVN, but only if the Windows 7 systems will again rename and rejoin the AD. I do most imaging right after school lets out and don’t have time to rejoin 200 systems manually.

If anyone has good news about a SVN release I can move to, I would REALLY appreciate it!

In a related issue, can we download a specific SVN release when we know it worked?

Thanks!

We have been using 0.32 since it was released and have a lab with old laptops in the back closet we use to fog various drives. They all use external USB connectors that we hook a SATA drive to and them send the image. Works great. The problem is we would like to migrate to 1.2. The server works fine but if we try and use the external USB connectors with the SATA drives it always says “hard disk not found.”

I am assuming there might be a config change I can make so the new Fog server can see external drives like 0.32 could. Any help would be appreciated.