It appears that the old host data is still in the database, so I’m not really sure where to go from here, if I should just suck it up or if maybe we can get it back.
I’ve not seen this. I’ve only heard of one other case of this, but it was during a time when the DB was plagued with all sorts of issues (because of my coding having some error or another).
This should not have happened to begin with, but it’s not something that’s a common occurrence and if it were, I’m sure it would’ve been posted all up and down the forums by now.
@apathetic_admin Don’t beat yourself up over something you didn’t know. What’s important is you asked for help where you needed it - instead of just giving up or being too proud to ask for help.
Part of being good in I.T. / comp-sci is knowing where to get answers.
I’ve added @Wayne-Workman’s code and actually (I think) improved upon the snapins creations/edits altogether. Hopefully this is properly solved. Thanks for the patience.
@Arrowhead-IT Removing the IP_ was exactly the fix. My printer mapped successfully both ways, locally, and via my samba share. This is good stuff.
@apathetic_admin I’m not sure if this helps you or not but creating TCP/IP definitions has been successful for me. The Samba directions via the Wiki were pretty straight forward. I really didn’t like the idea of placing a ton of printer drivers locally on my “master” images, so the Samba share worked great.
@Wayne-Workman Yeah, that’s why I’m trying to work out my issues now - this is a fresh upgrade on a new server (installed FOG on new hardware, then moved my snapins and database over). Only place I have the new client installed is on a new image I’m working on, so this is the time to get this worked out. Next I have to try and figure out why the old FOG clients aren’t auto-upgrading like I would have thought they would.
INSERT INTO snapinAssoc (saHostID,saSnapinID) SELECT hostID,122 FROM hosts WHERE hostOS=‘1’
This will only work on FOG <1.0, but here it is, in case anybody is searching the forum for something similar. In this case, my saSnapinID is 122, and we were looking for all hosts with a hostOS of 1 (which was XP).
Oddly enough, this problem fixed itself. All of the workstations are working just the way they are supposed to, no errors, images deployed just peachy. Going to chalk this one up to gremlins.
My current setup is that each snapin is actually a batch file that calls a generically named installer package. That way I can copy over new packages to the server without having to rebuild snapins inside of FOG.
It’s Windows 7, FOG .32, and whatever client ships with FOG.32. I have another Windows 7 image that does not have this behavior, so I have to think that it’s just something that I did differently, but I can’t fathom what it could be. I disabled UAC to see if that was the cause, but it is not. Perhaps I had UAC disabled when I built my first image, and this second one I did not disable UAC while building the image? I dunno.
