SUS Question 1

[sysadmin123]

Hi, I'm having a huge issue with IIS giving me an error everytime I try to run an .asp page. I've been trying to figure this out with no luck yet but I wondering...

Does anyone see any issues with installed SUS on a Windows XP Pro box and using that as my SUS machine? I have about 34 computers that would be hitting it throughout the org.

I've been running it off of our server which is also a domain controller. That's why I getting leary about trying all these changes trying to get it to work. I would rather just put it somewhere else anyways.

So what do you think?

 

[markdmac]

SUS will not run on Windows XP. SUS requires a minimum of Windows 2000 Server.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[godfra]

Hey Sysadmin123 - just recognised your nick from the other thread about an admin's checklist.

Like you I have also decided to implement SUS at our network, and found myself a bit stumped by the lack of idle Win2k servers.

My solution was to put win2k server onto an old 550mhz laptop - seems to have installed the OS and SUS ok, haven't tried the actual updating yet.

Just thought it might help to know someone else is going through the same things!

"Ring the alarm, another sound is dying" - Tenor Saw

 

[markdmac]

I would suggest you folks think about one other thing. SUS will really only be working at 3:00 AM if you have not altered the default settings. So as long as you have sufficient disk space for the update library, then there really isn't a problem adding SUS onto an existing server. (Unless of course you have a lot of peoploe working at 3:00AM)

Disclaimer: when I say "working" I am referring to consuming CPU time. The SUS services would always be running but my experience is that this represents a negligible impact on the server when not pushing out updates.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[sysadmin123]

We don't have any additional copies and I don't see my boss approved the purchase of it. Well time to see if I can figure out this issue.

Anyone know why I can't get asp pages to work?

 

[technome]

Disclaimer: when I say "working" I am referring to consuming CPU time. The SUS services would always be running but my experience is that this represents a negligible impact on the server when not pushing out updates."

True, but IIs absorbs memory.

 

[PSYSMIC]

Really sounds like a rights issue.

Of course, first check your browser. Might want to go ahead and set up a policy for IE to add the SUS site as a trusted zone domain wide, well minus servers.
Might want to check the execute permissions under the home directory tab for the virtual directory in question. IIS access permissions, NTFS permissions, and share permissions.

Quick and dirty test would be set permissions to everyone full access in each area, drop the security settins on your ie to low and see if it works. Just don't leave it that way...user might make use of it.

Is IIS 5 that ships w/ XP a different animal than IIS on win2k serv?