Topics created by Roger Saffle

@george1421 That was it. Thanks

details:
I had named the menu item HD Wipe
The config file said HD_Wipe
I used the GUI to rename HD Wipe to HD_Wipe and all worked well.

@george1421 Perfect thanks.

@Roger-Saffle There is nothing you need to do with fog, its your final destination OS that has control of the disk once it is launched.

FOG Image format wise there is no difference between a HDD, SSD, or NVMe drive once fog captures it. Once FOG deploys the image you will not be able to tell the if the source image was from a ssd, hdd, or vmdk file.

As a test deploy the same image to the 3 different disk structures (hdd, ssd, nvme drive). On the hdd you should get 50-90MB/s sequential speed using crystal disk mark. For the ssd you should get 350-520MB/s sequential speeds depending on your sata attached ssd. For the NVMe drive 700-900MB/s sequential transfer rates. All from the same source image.

Ok, i guess Ill just type them in again.

Just so you know Im not crazy, i pasted two lines in to a new xls from an old export and the one i did today, the orange is the missing tag.

0_1492026053382_upload-44406e12-4a1d-4372-9419-9e130e94a3c5 10-95-044-086 78:ac:c0:ae:61:56 4028 Hewlett-Packard HP Compaq 4000 Pro SFF PC
SE40-084-109 78:ac:c0:ae:61:56 Hewlett-Packard HP Compaq 4000 Pro SFF PC

@Roger-Saffle I’m just guessing that the ca was updated at some point either knowingly or unknown. I’d suggest updating the image that has the 0.9.10 client on it.

@Tom-Elliott same thing. BTW, no need to update both threads. Ill pop over to the other thread since its more on topic

https://forums.fogproject.org/topic/7848/sqlstate-42s22/1

@Roger-Saffle yes. absolutely you have to. and 0.9.10 is very, very old and has a ton of bugs.

Don’t forget that the machine account in AD has a password, this gets changed on a regular basis, this happens invisibly, it is a function of the way AD words.
From memory it gets changed every 30 days, and as I say is completely invisible to users and admins, the last changed date can be read from AD via LDAP, although it needs a bit of work to translate it into human readable format.
If you image a PC without sysprep, when you deploy that image it will not join the domain if the machine account password has changed.
This will need the PC to be deleted and re-added to AD to resolve.

Got it thanks. Trying to trouble shoot AD not working. We never had a AD before, we were eDir. The machines manually join or will join with power shell. Thanks. so now I know when it renames it should join. Will help with my trouble shooting.

Bump, hope we can find a way… @Tom-Elliott, @Wayne-Workman?

Spoke to soon.
Wrong data in the columns. Note image ID and image Name. Then it just gets worse.
Capture.JPG

@Roger-Saffle Make sure you use the same IP as the old main, and same name.

How about…

Apply the snapin to everyone,

Then, in your script, just specify computer names… if the computers name matches such-n-such, install the font.

Clean up the snapinJobs/snapinTasks tables.

No payment but I mean requesting the ability to do a :runas override

Actually it would still be allowed because fog does not install software or printers as the logged in user. It installs using the system user which is essentially the root user of system level activities allowing printers and software to be installed but maintaining user level permissions.

We put it on our images too. But if you choose Fog printer management to Add/Delete it deletes the Smart Printer. I either need to know how to push it out or how to keep from from deleting it.

We need a wiki article on Printer Management.

Tom,
If I left those two fields blank, the snapin seems to run just fine.

I figured it out. We had inf files on our server that we used to install printers via batch files. I tried to use those same inf. For some reason they did not work. I reinstalled the exe that installed the inf files on the local machine. Pointing fog to these clean installs of INF files worked.