We make our images on a VM. We pull that image down to both HDD and SSD. Both come down and boot just fine. I have read a couple places online stating that if you clone a HDD to a SSD then your PC wont take full advantage of the SSD speed.
Is there something I need to do to make sure my SSD drives imaged in fog are all set?
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.
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
If I collect the Other Tag 1 info on a csv, can it be uploaded and added to the existing host?
@Tom-Elliott
we do not really use other tag 2. We use other tag 1 as the asset ID when doing a fog host import.
Looked in the database, and the iOtherTag1 is indead blank on a majority of host. Ill look in iOtherTag when I get back to my desk.
edit: Looked in database iOtherTag is blank for those machines missing “Other Tag 1” on the inventory export.
When doing a inventory report, 85% of our host have no “other tag 1”. This field is blank. Had this problem, though only an handful, when we did a report for inventory last year, but we took the time to type them back in. Ill type them back in yet again, but is there a known issue with the inventory extract?
My problem is that I we are a school district. Thus I cant donate. I also cant use school funds to buy shirts. I need a invoice. I wish there was a way to get an invoice from FOG for development or support. Ive asked but the amazing people at FOG dont feel the need to invoice me. Thus i use this amazing product and do not have a way to help fund it.
just a heads up incase you didnt know, Chromium has been discontinued and replaced by CUB due to name issue complaints by Google. I havent looked at CUB and dont know how similar the are.
That what we do. The macs are on the side of the box along with a bar coded version of the MAC. We use a scanner to scan them into google docs.
@Tom-Elliott
it seems to be very limited to some machines with 9.10 or older. All of the machines i checked that had client 0.9.12 have upgraded to 0.11 . I manually upgraded the 0.9.10 to 0.11 and the error went away. Ill just deal with those as i see them. They must have been having the error a while to never move past 0.9.10 as we have client update on for everyone.
Thanks.