Ignite Quit Receiving MOS Updates

Our Ignite system quit receiving MOS updates. Scriptviewer had nothing also.  We suspected the gateway pc at first. 

I went to ENPS and cleared the queue  and MOS deactivated all of the rundowns.  I then reactivated the MOS on the rundowns and the queue immediately built back up.

Pinging ENPS from the gateway failed as well as pinging the main ignite computer.  Must be the Firebox has died.

restarting the Firebox failed. It never came back up.

Added a second NIC to the gateway pc. Changed the original NIC ip address to above 192.168.0.100 and made the addin NIC to be on the same subnet as the ENPS server.

Then in Scriptviewer I went to ScriptList and News Server Setup.  I changed the ip address  in ENPS MOS to match the 192 ip in the gateway then click on build and ok

Next was to change the ip in ignite.  Go to Setup > News Servers.  Again ENPS Mos to the 192 ip and build.  Then a quick restart and all was back up. scripts were showing up and everything was updating as it should.

Checked the queue in ENPS and it had filtered itself out. But I did not think that would happen until after rundowns were deactivated and reactivated.

New Printer Woes

So we got a new copier/pinter/scanner/fax machine.  I have not had to do much printer replacement and this was a real eye opener.  First off I had the printer installed using the same name and IP as the old copier.  Because this went to all of the staff I was getting reports of problems printing all over the building.  ENPS had problems opening ENPS.  It was failing to open at the point of loading the printers.

Hindsight being 20/20, I should have installed the printer to another IP address and called it another name.  I could have then changed the logon script to reflect the changes.

But how I resolved it, I looked up the print driver and found it in: "C:\WINDOWS\system32\spool\drivers\w32x86\3".  This was a Kyocera Mita copier and all of the drivers started with KM... and it is the only printer of this brand.  So all other printers did not have this prefix on the drivers.

I then rebooted into safe mode and deleted the files.  Then on the next logon the printer got remapped and started working.

Glacial search times in ENPS.

If your ENPS system has long search times resulting in "server unavailable", try this.

First off, I recommend doing this on the buddy server first. This will not affect your primary server when you do so.

Go to Computer management and choose Services and Applications. Then look for the Indexing Service. Highlight the Indexing Service and make sure that there are no Docs to Index. Then go to F:\NOM and find indexdel.exe Double click this and there will be a message confirming you want to delete the index. Say OK and the Index will be deleted. Go back to computer management and look at the Docs to Index. It will begin climbing. The system will re-index everything in ENPS and you will not be able to search for anything during this time.

After it has finished (several hours later) switch to your buddy server and see if your search times have become very quick again. If so, repeat for the process for the primary server. Remember to keep everyone on the buddy so that they can search normally while the primary is being re-indexed.

If this doesn't fix it call ENPS.