So my updates broke, because I “accidentally deleted” a computer group in the WSUS console (http://msmvps.com/blogs/athif/archive/2005/09/26/67958.aspx). When I went into the SBS 2008 console and went to Updates, and tried clicking the “change the software update settings” in order to make any changes to my computers and exclusions, I was greeted with the error “windows sbs 2008 console has stopped working”.
For those of you that are system administrators and have to keep up on 3rd party software updates, check out www.calendarofupdates.com. I don’t know what I would do without it. I check it daily, of course.
WebEx sure makes it hard to find the right msi files for GPO deployment. Here’s the trick: go to http://webexhelp.webex.com. Click on Meeting Center tab, then Support/Downloads and grab the Meeting Center Application for both IE and Firefox in msi format. Could they make it any harder?
For GotoMeeting, see http://support.citrixonline.com/GoToMeeting/search?search=msi
Say goodbye to replmon, say hello to repadmin. Gone are the days of good old replmon, so to force AD replication across site boundaries and all just do the following at the command line:
repadmin/syncall /APed
This script will take ownership of all files and grant you permissions to them if you are having trouble with file permissions. Name it mine.bat:
::Mine
::Usage mine.bat “c:\documents and settings\user\my documents”
::Created by Jason Knight
::10/02/2007
takeown /F %1 /R /D y
cacls %1 /G administrators:F /t
Now all you have to do from the command prompt is:
mine <path to files/folders>
Use the following code snippet in the address bar of Firefox to reveal any passwords you need to reveal on the page you are on, just paste it into the address bar and hit enter and watch the magic…
javascript:(function(){var%20s,F,j,f,i;s=”";F=document.forms;for(j=0;j<F.length;++j){f=F[j];for(i=0;i<f.length;++i){if(f[i].type.toLowerCase()==”password”)s+=f[i].value+”\n”;}}if(s)alert(“Password%20is:\n\n”+s);else%20alert(“No%20passwords”);})();
Please note that this does not work on ALL password fields, but a lot of them it does!
And any other P2P software. I’ve seen multiple threads on this around the internet about blocking the port it’s using. The thing about these P2P clients is that they can use any custom port or range of ports! Sure fire way:
Get a “business-class” or at least “semi-business-class” firewall, like the ZyXel ZyWall, and subnet your network. Create a DMZ, and assign the ports to the DMZ. Anything your connect to the port will inherit what you permit from the DMZ to WAN. If there is an “any” rule for TCP/UDP ports, remove it, and block all ports from DMZ to WAN. Then open ports 80, 443 and 53 (both TCP and UDP for DNS), and off you go. Nothing will work except web browsing, which for most wireless, open networks, is all they need. Hook your wireless access point up to a DMZ port and you’ve stopped all traffic except what you want to allow. I’m not aware of any torrent app that falls back to ports 80 or 443, but I could be wrong. Comment if you have any experience with that one.
This is a great flash player system for any website. It uses mySQL and stores playlists and includes a customizable player with embed code for any site. I use PHP based sites personally, but I believe it can be embedded in HTML as well. Their website is http://www.flamplayer.com, and you can get the latest downloads there. The reason for this article is to clarify a few settings that seem to be lacking from the installation instructions at their site.
That pesky sylink.xml file again… We had to reinstall our SEPM server, which left a lot of clients stranded. Well, rather than go around and reinstall on all the clients, which doesn’t work anyway, here’s a better way to update them. The file, sylink.xml contains the entire configuration, so obtain a copy from a workstation that is successfully connected to the SEPM server in the group you want. The file is located at c:\program files\symantec\symantec endpoint protection\sylink.xml. Now that you have a good working copy, let’s move ahead.
Use a tool such as psexec to attach to the machine, or just pull them up with computer management, remotely. Either via command prompt or compmgmt.msc, kill the “Symantec Management Client” aka smc.exe. Using psexec, it’s smc.exe -stop. Now either delete or rename sylink.xml and copy over the spare copy you hold in your hands. Restart the SMC service (psexec, smc.exe -start). Check your server for the new workstation and move it into the proper group if needed!
So I recently had a customer’s network go down. Usually not a HUGE deal, but in this case, the company was running SBS 2008, so yes, big HUGE deal!
