Posts made by apathetic_admin

Unfortunately there are 500 or so hosts that are still using XP. I should have mentioned before, I’m still on .32 , so the OS association is still by host I think.

I’m trying to come up with a mysql query that would do this, but I’m outside my comfort zone for sure. I have a snapin that I need to deploy to all hosts that have XP for their OS. I was originally going to create a group of XP machines, but I couldn’t group them by OS. I have a list of hostIDs of machines that are XP, but I’m not sure how to go about creating the mysql query to do this.

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.

I understand what lsass.exe is doing, and I’ve found quite a few leads on it, my real confusion is just on what is going on in this particular instance. I updated the image for computer model A on PC1, uploaded, and pushed it to PC2 (same model) and got the error I indicated above. However, I then zeroed out PC1’s hard drive, redeployed that image to PC1 (that was build on PC1) and I have no problems.

Decided I’d go back through and grab a couple of our XP models and push out the most up to date pre-sysprepped image that I had, run Windows Update to grab the final updates (about 6-8 months worth) and then sysprep and upload. When deployed to any machine other than the one the image was created on, I get the dialog box shown in the attached image when it should be going to mini-setup.

The first time it happened, I made the assumption that I had a corrupt image, but with a second image totally different image doing it as well, I have to assume that it is something else. The only thing that I can come up with is something in the last 6-8 months of Windows patches.

Has anyone else run into this?

Also, to save anyone the question, I have googled the issue, and no, it is not any sort of worm or malware.

In the next two or three months we are finally supposed to have everything in place so that I can start pushing Windows 7 out to these machines, but in the meantime, I have a need to reimage a ton of them and was hoping to have them as up to date as I could.

[url=“/_imported_xf_attachments/0/838_lsass.png?:”]lsass.png[/url]

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.

Has anybody experimented with this? I’ve been thinking that I could install Chocolatey ([url]http://chocolatey.org/[/url]) in my base image, and then my snapins could just call Chocolatey to install the package. That way I don’t have to do the work of keeping up with updating my snapins all the time.

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.

[quote=“chad-bisd, post: 15972, member: 18”]I believe I moved this thread because it’s not a FOG problem per se, but more of a general networking/os configuration issue.[/quote]
Oh cool, that makes sense.

[quote=“chad-bisd, post: 15972, member: 18”]I think the easiest thing for you to do is to make multiple FOG servers. Leave your first FOG server as the (M)ain server and install a FOG server in (S)torage mode for each VLAN. Make a storage group for each VLAN, and make a storage node in the storage group for each VLAN.

In other words, if you have 5 different VLAN’s/Subnets you want to multicast with FOG, you’ll have 6 servers. The main server, and a storage node in each VLAN. You’ll store the image for each subnet on the storage node in the storage group for that subnet.

I have a similar setup, but I have multiple storage groups setup, and each storage group has one storage node in it. I do this so I can unicast a group while uploading another image, or unicast to multiple groups without slowing the system down. I’m thinking you could do something similar, but with the intent to be multicast.

Since you are multicasting, you don’t need much of a machine, it could even be a VM. Multicasting requires more memory on the server than unicasting does, but unicasting requires a better disk subsystem.

I’ll be happy to advise on how to set this up if you want, or you can continue trying to setup and configure the way you originally asked about.[/quote]

Gosh, there really isn’t a cleaner way than that to do this? I was hoping there’d be a way I could accomplish it with one server with multiple virtual IPs and having the different services listening on all of them.

My fog.log file is this, over and over again:

9/11/2013 2:54 PM FOG::GUIWatcher Message found, attempting to notify GUI!
9/11/2013 2:54 PM FOG::GUIWatcher Dispatch Failed!

Running tail on the log, I see it posting seemingly once a second, 24/7. All of the Windows 7 machines that I recently imaged do this. It makes it somewhat difficult to use fog.log to troubleshoot other issues.

[quote=“Tom Elliott, post: 15657, member: 7271”]Happy Paste Eating![/quote]

Ha thanks man, it’s an acquired taste.

[quote=“chad-bisd, post: 15739, member: 18”]Tell your network guys to turn on IGMP snooping so that the network equipment only sends multicast traffic to interfaces that request it. They may have to setup multicast groups or multicast profiles depending on the make/model/revision of networking equipment you have.

You only need to have multiple interfaces on the FOG server if you actually create untagged VLAN ports on the switch for each group. Untagged ports basically act as a separate switch. Like if you had your FOG server and 4 workstations plugged into ports 1-5 and they were all untagged VLAN 20. They could only talk to each other and nothing else on the switch. If you tag those ports to the other VLANS, then any device that understands tagging (802.1Q I think) can decide for itself if the traffic belongs to it.

To be able to help you, I think we need more concrete details.

Your subnetting/VLAN info to start. I’ll assume you are using private addressing (10.x.x.x, 172.16.x.x, or 192,168.x.x) right?[/quote]

Apologies for the delay, I’ve been out of town; also, I’m not sure why I put this thread under “Linux Problems.”

I have the FOG server on a VLAN, say VLAN 40, with an IP of 10.85.40.4. I have several rooms of a few hundred pcs each, say 10.85.30.x, .31.x, .32.x, and so on. All of the clients are plugging into a Cisco 4510 (each room on it’s own VLAN), and the FOG server is on another switch.

While it may be possible to multicast across VLANs without having an interface on each one, my supervisor and our network/linux admin told me that we did. I’m just the Windows admin who came from eating paste in the corner to try and make my life easier, and then I can go back to eating paste.

I currently have around 600 workstations on one floor that I use FOG with. Previously all of them were on one VLAN with a very large DHCP scope. As part of a network overhaul, we are separating different areas into different subnets. In order for multicasting to work, as far as I can tell, I need to have an interface for FOG on each of those subnets.

My subject basically says it all: in order to do multicasting across a fairly complex network for all of our call center workstations I need FOG to be available on multiple subnets.

In my research via google, I have found a few helpful tips but nothing concrete. I noticed, for once, that the registration option via the PXE menu has the ip of the web service that the information is relayed to embedded in it, didn’t know if there was a way around that without having an option on the PXE menu for each subnet. Also TFTP doesn’t seem to respond on the original interface if the secondary interface is even up, let alone if it’s configured to use it.

I’m hoping that with help from you all I can figure this all out, and then document it and stick it in the wiki someplace.

Do you have the FOG client installed? How is your snapin configured?

We have hylafax setup here for faxing, and I’m looking for a hylafax client that will work well being deployed as a snapin. Has anyone accomplished this goal before in this manner? If so, what client did you use? There seem to be a plethora of hylafax clients out there, but none of them are friendly to mass silent deployment.

Does anyone know of a way to increase the maximum amount of characters I can put in for the field length for snap in arguments? I have an eFax client that can be installed silently but needs quite a few command line arguments and they are getting cut off.

That is a ridiculously simple and awesome solution, thanks!

I’ve been trying to make a snapin for the newest version of Adobe Flash. I’m pushing it out to 32bit XP machines. Originally I just installed it on a machine and made the snapin using installrite, but that doesn’t seem to work anymore. After running the snapin and it says it completed successfully it’s not there. I’ve made dozens of successful snapins with this before and this is the first issue I have run into.

I decided that I would just use the executable that Adobe provides and give it the “-install” option which, according to what I read on their site, should force a silent install mode. I believe, however, that the option does not work with version 11. Has anyone had any similar issues, and if so, what did you do to resolve it? I have around 350 machines that I need to deploy this to fairly soon.

[URL=‘http://support.microsoft.com/kb/314082’]Is it this? [/URL]