SwimmerB

So here is my issue, I would like to set up a new server with WSUS 3 that uses a SQL backend. From all the documentation that I read it seems like the requirement is in place that I need the SQL server in an AD domain. Has anyone done it without AD and if so how.

Yeah that was my guess as well to do. I was trying to get away from duplicating the policy but it is not that hard to do so sounds good to me.

Ok, I have a slight issue when applying a windows firwall reg key the add exceptions to the registry at path [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List] my issue lies in the fact that on some of my systems this works and others it doesn't. I have read that the DomainProfile part of this can be when you have a domain controller on your network, but if you do not have that then use StandardProfile setting. What I am wondering since some of my machines could be in the domain and other are not will using just the standard profile work for domain machines or does it then only look at the domain profile. If this is the case I can just cover all the bases and add it to both but don't really want to. Any insight would be great. Thanks

I have used a program just a few times called autologon. This can be gotten from sysinternals. I have also used a program that I think can be found on Novell's site that could do what you need call autolog. This adds novell stuff to but don't need to turn it on.

Downgrading a few versions is not the most preferable method but may be just the solution. I talked to my other technician and v 6 was still having issues. I thought of going down further. Maybe I just might do that. It 's kind of odd that the longer the program is around the farther back in versions you have to go to get a good version! Oh well I thin this might be the acceptable answer.

Downloading the PDF and then opening does fix the problem but does not give us a very viable solution. In the environment I am in they have lots of CAD apps that open drawings using adobe reader. I will have to find out about moving down a version did not think of that. Very frustrating, I see lots of posts for this issue but same old fix that works for a while then will end up broke again.

We do have the most current virus definitions and updates on the workstations. Have not seen any infection of the machines that the issues arises on. Also the fix I referred to earlier that is a temporary solution is to go into the preferences and then under the Internet category un-check the display in browser option. But after say a random amount of time this craps out again.

I have got an issue with adobe's acrobat reader where at random times when trying to open a pdf inside internet explorer reader errors out saying that there was an external handler error. The message goes something like this. Could not find External Window Handler. An internal; error has occurred. I am using Windows XP SP2 and reader v7. In my current environment we use many CAD applications and this error also occurs when viewing drawings from within those programs using reader. I have searched on adobe's site and the only solution I come upon is to force reader to open program in its own application not within the window. This seems to work for a bit then still craps out. A reinstall of reader works for a while the comes back again. Anyone else had this problem? Thanks

I have not seen this specific sort of problem before on a home PC but in a network environment if there are mapped network drives on your machine with letters right after the local then there can be issues with the usb drive. I have not seen this for the cd rom though. Should check first to see if this is the case. EXample might be c:(hard drive) then d:(Network driveA) , e:(Network driveB). This could cause issue and when you reboot with media already in computer will add that then not show mapped drive. Other issue could be something wrong with the motherboard possibly. Maybe there is a bios upgrade that might fix your issue. Never have seen this before but possible I guess. Last question is was it working prior to XPSP2 on that same machine? I hope my ideas is some help to you.

Another thing you could try doing is add that script to the local group policy. That way if you have it run on logon then it will try to run that script. You can get to the local group policy by typing gpedit.msc in the run box then just add the script to the the logon/logoff area under the user config then windows settings area. I'm not sure but it would probably try to run it everytime but I don't think that should cause much problem.