Neowin.net

Internet Security Manager is an utility that customizes different features of the Internet Explorer Web browser. It's a snap to use and provides the tools you need to retain and manage your Web browser settings.

Internet Security Manager sowftware lets you disable individual menu items and disable individual tabs in the Internet Options dialog, as well as specific settings from each tab. It prevents others from editing your Favorites. Still other settings let you change the title caption, toolbar background, and animated icon; change default folders; and replace standard error information pages, etc. Besides it has an excellent feature to avoid annoying popup-windows from ever being displayed. The powerful "Web Spy" feature enables you control WHAT web sites and WHEN users may view. Internet Security Manager has the "Password control" and "Time control" options, which enable you to flexible manage disallowed sites.

If a user leaves a page up on IE Browser and then is away from the computer for some time you can make the browser to go back to the default page after a certain time of the user inactivity. Internet Security Manager software support "multiuser" and password protection are also offered. This is great for managing network machines and the import/export functions let you store program settings in an external file. Internet Security Manager it's great assistant for fine tuning your's security options of Internet Explorer browser.

News source: Internet Security Manager Home Page
Screenshot: Internet Security Manager 2.2
Download: Internet Security Manager 2.2

eWeek: What technologies from the upcoming Yukon database will be found in Windows?

Allchin: The operating system needs to understand people at a rich level and elevate them to data-class objects. Yukon allows all data to be marked up, common schemas to be defined and the information to be natively stored. We need to do all this, and it's very tough. We're learning as we do it. There's no question Longhorn [the next version of Windows] is a long way off because, as we do the schemas, we are looking at how things will be stored efficiently and whether dynamic indices can be carried on the fly, etc. The next stage will be a Professional Developers Conference held towards the middle of next year where pieces of code are handed out for people to start playing with. This will cover our new 3-D [three-dimensional] stuff and all the Longhorn-managed APIs. Yukon is going fine, but as we find things, we realize we have a lot more work to do on this for Longhorn. The trick is bringing it all together.

eWeek: Microsoft has talked a lot about the new storage system to be found in Yukon and said some of those technologies will be used in Longhorn. Will that technology be found in the upcoming Windows .Net 2003 servers?

Allchin: No, there's a separate team working on what we call WinFS [Windows File System] and a separate team working on Yukon. There's obviously a lot of technology flowing between them, but none of that is in Windows .Net Server. But there's so much else in the .Net servers. I think the idea of roles and the ability to quickly be able to say that one is a file server, another a Web server, another a [Domain Name System] server—and have the system configure to the minimal configuration from a security lock-down situation and being able to use it in that mode—is a big push towards simplicity. I love the improvements we've made in ASP [Active Server Pages] .Net around the whole process model and what you can do with process groupings and the performance gains to be had with that. The streaming media server is incredible and is included in the .Net server. That's a big advancement in terms of infrastructure.

eWeek: Is your goal still to release the Longhorn client and server at the same time? When do you expect that to be?

Allchin: That's still my goal, but so much can change. Some of our designers are already working on the Longhorn server, thinking about new event systems and the like. But it's just too early to say when it'll be ready for release. We know the vision, and we have huge teams moving ahead on the different pieces. We do have Longhorn builds, but we're still a long, long way away.

eWeek: What is really exciting for you in Longhorn, particularly around the next-generation technology for the enterprise?

Allchin: There's a bunch of work going on around what I call concrete plumbing, covering things like hot patching—the ability to keep machines running while you patch them—to all the work we're doing on standardized install. On the networking side, we have many ideas around how to create ad hoc groups on the fly. For example, if several laptops are in a room for a meeting, we want the PowerPoint presentations to be able to show up on all of them concurrently, to be able to project those up to the projector wirelessly or to synchronize what they're doing so they can make notes without having to do any setup to get the dynamic bonding in a secure way.

We have a lot of ideas about making the system simpler. Automation is our dream, not just of the business processes but also to have the machines automate and self-heal themselves.

On the client side, the visualization capability that you'll be able to do with our new 3-D technology will really help knowledge workers. My dream is that the client never stops running, has integrated communications built in, great visualization capabilities and a lot of flexibility. I'm as excited as I've ever been about where the PC and the server are going.

eWeek: What are your plans for reintroducing Smart Tags into Longhorn?

Allchin: I haven't given up on that idea but have given it no thought since it got removed from Windows XP. It's not that big a deal, and it was so surprising to me that it caused so much consternation. But I learned that it's a serious issue, and when we go decide on this, we'll bring all those people concerned about copyright and other issues in and discuss it with them.