As part of our migration from SBS2k3 to SBS2k8 (and a completely different domain) I elected to move all of our printers to a central print server and push them out to the client PCs via a group policy rather than manually walking to each PC and setting each printer up. For non-Vista PCs, this requires the client to run PushPrinterConnections.exe on startup (or login, depending on how you set up your GP) to actually set up the printers.
In a typically Microsoft fashion, the gurus at Redmond ignored the feedback on the beta SBS 2008 forums and neglected to put an i386 version of PPC.exe on the x64 server installations, and as none of our client PCs run 64bit Windows XP, this caused some problems (read: nothing worked). (more…)
While setting up some backup scripts for a windows server (using NasBackup - go go gadget free plug) I realized I should also be backing up certain registry keys to go along with the files. Clearly a solution that could be initiated from command line (in a bash batch script as I can’t write VBscript and don’t want to learn) would be the best option.
(more…)
Over the weekend, one of my backup scripts started erroring out while sending the backups offsite to an FTP server. The error message was:
200 Port command successful
150 Opening data channel for file transfer.
netout: Broken pipe
550 can't access file.
(more…)
Sometimes IIS manager takes 10-20 seconds to load, and when it is finally loaded it has no server connected (and therefore no websites). Apparently this is fairly common on Sharepoint 2007 servers, and the fix is to restart the sharepoint timer service, but I do not run sharepoint.
As a side effect of this problem with IIS, my HELM 4 control panel stops responding, possibly because it is in its own application pool. In the past I have had to reboot the server to get everything working again, but I can’t keep doing that with a production server. Restarting the IIS Admin service in Service Manager hangs and eventually fails trying to stop the World Wide Web Publishing service.
(more…)
I just installed PHP 5 on a windows 2003 server running IIS 6 and found that none of my extentions were loading correctly. Upon further inspection of the phpinfo() command, I found the following:
Configuration File (php.ini) Path C:\WINDOWS
Loaded Configuration File (none)
So PHP had decided not to use the php.ini file that was located in the working directory, but rather attempt to use one from C:\Windows, and because it could not find one there it was using the default setup. Initially I put a symlink from c:\windows\php.ini to the real php.ini file, but that did not appear to work either.
(more…)
