itwasntme

I log all logins in to a text file purely to make it easier on myself when I need to find where someone has logged in. I didn't notice the change until a few days afterwards and it took me a few days to work out exactly what I had done that made this change - I'm still not sure WHY it made this change. To see an example of the format of the text file I log to please see the code snippet below; Set WshNetwork = WScript.CreateObject("WScript.Network") msgbox(ucase(WshNetwork.ComputerName) & " " & lcase(WshNetwork.UserName) & " " & WeekdayName(Weekday(Date)) & " " & Date & " " & Time) The first example here is with SP3 installed; mypc myusername Thursday 7/10/2008 1:00:35 PM This example here is after uninstalling SP3; mypc myusername Thursday 10/07/2008 13:19:20 So SP3 seems to americanize the date and time? I have no idea why this change happened, as far as I can tell there were no changes at all to Regional/Locale options and I don't see reference in the SP3 notes for such a change either. I was looking to deploy SP3 this summer with SCCM (SMS Successor for those that are not aware) but I am not happy about this change. Anyone have any ideas? or anyone noticed any other anomalies with SP3?

I'm not too worried about embedded flash, they are taught to use flash unfortunately. Executables were all I was really worried about, it's something that's always bugged me tbh. Currently students cannot access any pen drives, but I'm trying to do all I can to protect things in preperation for enabling pen drives again.

Thanks but I think I have it working now, it was easier than I expected. I'm sure I will find out in the next few days if I've broken any other software with these policies. I have attached a screenie;

Ok, so we can prevent students running applications (you define what is considered an application) from their user areas/home drives/pen drives etc using a combination of Fileserver resource manager (2003 R2) and software restriction policies. But how do you guys stop students executing applications they've embedded in word (and potentially any office application or any other OLE capable app) documents? I figured the best way to do that was to identify where it launches from, and I find it points to docs & settings\username\local settings\temporary internet files\blah blah. So I figure I can use software restriction policies to restrict C:\Documents and Settings\. This works.... however... applications with shortcuts in docs and settings\all users\start menu or even desktop for that matter won't launch now... Alrighty, so now we'll create another software restriction policy, this time 'unrestricted' for docs and settings\all users - well, that's great... right? I admit I haven't tested many applications, however I do know of one application called InPage Urdu (some crazy app to type backards/in urdu) when launched appears to create/launch something in the users temp folder. So, what I'm interested in is have any of you guys got any suggestions/tips for how you stop students accessing executables?

Have the same difficulty here, pretty much identical except we're using nortel ap's. As you say, it just forgets settings. Logging on to the laptop while wired refreshes the policy and all is good again - for a while. I've been trying to understand if there is any pattern to it, i.e. is it the same laptops losing settings each time? Could it be that the laptops losing the settings are laptops that perhaps haven't been logged on to at all for XX days, and some thing gets reset in this time (thinking along the lines of dhcp scavenging although I know radius is not supposed to work like this). All dell latitude d531s here with intel a/g cards using the windows zero service.

They could enter an alternative LEA proxy which would bypass our logging proxy. I think I may have got it sorted out, by messing around with intranet zone info, I'll post when I'm sure.

I've looked through it but I cannot imagine what would be wrong here, I mean, if it works without a problem when on the school network, and on home PCs, yet not on a domain pc on home network, what would I expect to find fault with in IIS?

This only happens using a teacher laptop at home, any other computer (not a member of the domain) will access it fine, just as any domain PC (including teacher laptop) has no issue connecting when on the school's network. To re-emphasise the point, I do not expect any problem to be with my script, or whether proxy is turned on/off but rather I believe some other function somewhere is confusing the matter. I do appreciate the efforts so far, and perhaps I have not explained the difficulty very well - which is part of the reason I have had no success in 'googleing' this problem. https://domainname/ resolves but shows page not found (regardless of location) https://ipaddress/ shows page not found (regardless of location) http://domainname/ tells me i must use https (regardless of location) http://ipaddress/ tells me i must use https (regardless of location) http://domainname/owa tells me i must use https (regardless of location) http://ipaddress/owa tells me i must use https (regardless of location) https://ipaddress/owa displays fine (regardless of location) https://domainname/owa displays on laptop when in school, displays on all PCs outside of school. However, teacher laptops (members of the school domain), when not connected to the school domain, are unable to get this page (and it has just occurred to me I need to double check the response code, but is either blank or 404 I'm sure).

It doesn't appear to be a fault of the proxy settings anyway, as even taking out all proxy information when at home still has this oddity when connecting to OWA through IE.

We do not want to allow staff to change proxies themselves, they inevitably get it wrong and cry that nothing works. It would also allow them to use a parent proxy instead of our inhouse proxies.

In 2007, it switched to /owa

I thought this would work too, but tried it and was unsuccessful. Later I realised it makes sense that this change shouldn't work since; I just cannot understand why I'm having this problem, I've spent some time hunting through the registry and the only references to /owa are inside recently visited websites etc. I have looked at trusted/intranet zones and been playing around in here to see if this has anything to do with it but I can't understand why it should anyway.

@Geoff - I had not expected the problem to be with the proxy.pac file, I posted it rather than just stating 'I use a pac file' and having people reply that I should include it in original message @fafster - I would prefer not to upgrade to IE7 at least not for the timebeing Any other suggestions?

None of you guys have any idea about this problem? If someone there is thinking 'duh this is so obvious but I will spare this guys shame by letting him work it out himself', please put me out of my misery Alternatively - did I post in the wrong section perhaps?

I am trying to give staff access to internet on their school laptops at home but am running in to a problem. I have experimented with vbs scripts and with pac files and have since decided I prefer the proxy pac method. IE6 with all latest updates installed and used in all instances; So, here is my proxy code (I have replaced my domain with 'mydomain' in all parts of this post) function FindProxyForURL(url, host) { if ( !isInNet(myIpAddress(), "10.112.0.0", "255.255.0.0") || isInNet(host, "10.112.0.0", "255.255.0.0") || dnsDomainIs(host, ".mydomain.local") || isPlainHostName(host) || shExpMatch(host, "*portal.mydomain.com*") ) return "DIRECT"; return "PROXY myproxy:8080"; } This works flawlessly at home with one exception - the school OWA (may be worth noting that I had the same problem when using a VBS script also). https://mail.mydomain.com/owa returns a 404 page (not expected) https://mail.mydomain.com/ returns a default IIS page (expected) http://mail.mydomain.com/owa returns the page saying can only be accessed with https etc (expected) https://99.99.99.99/ returns default IIS page (expected) https://99.99.99.99/owa gives me email working perfectly (expected) nslookup resolves IP address correctly for OWA external address I have checked that hosts file does not contain any entries for 'mydomain', I have checked intranet/restricted/trusted zones in IE and mydomain is not listed. Exchange 2007 installed on Server 2003 Enterprise Any other information I'm missing? Anyone come across this anomaly? Have I missed something very obvious?