Cloud Security, Privacy and Reliability...

Security, Community and a whole lot more!

Blogs

Calgary - TechNet Winter Tour 2005!

  • Comments 2
  • Likes

It was fantastic to be back and so many of you I met on the last tour came up and said Hi - what a welcome!..... I was looking forward to the great weather I was told you guys were having..... it snowed for my arrival and now it is snowing for my departure from your fair city :-).... Ahh well, I shall just have to come back in the summer! (as long as I don't bring the snow with me again I hear your cry!)

Not that we noticed anything of that for the event where we had an awesome gathering of over 330 people! I had an amazing time and I hope you did too. I spent some time going over the feedback forms last night ans just want to thank you all for your comments and encouragement for the event and especially the new format - you guys rock! I was also very impressed and the gentleman who correctly guessed my nationality (Now Canadian)!

I really am looking forward to coming back here again in the near future - see you all soon and enjoy! Don't forget the chat...

TechNet Winter Tour 2005 Technical Chats – Calgary
Add to Calendar

Tell A Friend

March 18, 2005
9:30 A.M. Local time

Additional Time Zones

Enter Chat Room

Comments
  • I would just like to say thanks for the great session. I found it to be very informative and practical. The information that I took in will be put to good use in our office.
    Thanks again Bruce.

  • Hi Bruce. As per our conversation at the Calgary Technet (great job by the way.. your breadth of knowledge is really impressive) I asked about how to restrict certain users by Computer and User OU to have no access to the external internet. Here is the scope:

    All users running XP SP1 and SP2. Servers are 2003. Have created a restricted user OU. ISA not an option. Firewall is Cisco PIX. My initial elegant thought was to restrict users through the Restricted sites policy by setting it to deny access to all sites (eg http://*.*., *://* etc). I discovered however that Microsoft does not allow the use of wildcards when defining sites to block. Obviously it would be impracticle to define sites manually.Additionally we have a requirement for users to be able to access the internal portal. Additionally, by using the proposed block, users would be unable to once connected to the portal change the url to an external site.

    Unfortunely the client is too large to restrict (deny) all users and create exception OU's. Any suggestions on how I might accomplish this task? Any ideas on a way to script around wild cards?

    Regards,