testing server load
How to disable workstation from saving win2000 server mandatory roaming profile also as local profile?
Hi all. Tricky question: I have a perfectly running win2000 domain with 1 server and some workstations. I've set up mandatory profile for each user because I want to regulate how their desktop looks like. I log in on a WS and yes it loads the mandatory roaming profile. I see the icons that I have to see. Now as a user just to test it I create a text file and let's say a shortcut on the desktop. That's fine I want users to do that. I log out of the domain - and I'm expecting all these two new icons to go away since I'm using mandatory profiles but when I log back in THEY ARE STILL THERE. I need to somehow find out how to create a profile for all the users - and by the way I want them to use the same username, no password - that they are FORCED to use and after logging out and back in they would loose all the changes that they have done. But I want them to be able to save files on the desktop so I don't want to take off write permission from desktop. Any idea guys? Thanks a lot!
Even if you are using a mandatory roaming profile, this does not preven users from making changes.
I think what direction you should be going, along with your mandatory profiles are group policies.
In Group Policies, you can prevent users from doing things to the desktop and lock out many features to users in WIndows.
Another suggestion along with your mandatory roaming profiles. Make your users restricted and they won't be able to save to the desktop, etc.
I think with the mandatory profiles and the group policy, you will be open to using more than one username for everyone.
Network Design and Proof of Concept Testing
Overview
All design changes you make to your network must be tested with a proof of concept plan. It is important to test the current design, configuration and IOS versions in a non-production environment or on the production network with limited disruption. Implementation of newer network modules at a router, for instance, could require that you change the current IOS version that is implemented. Making those changes could affect WAN or campus modules already installed at production routers. That is the real value of doing a proof of concept and certifying that the new equipment and IOS versions integrate with each device as well as the network.
Advantages
The following list describes the advantages of doing a proof of concept with your network design. The proof of concept test results should be examined and used to modify current infrastructure, security and management specifications before generating a design proposal. The proof of concept model suggested here involves prototype design, equipment provisioning, defining tests, building equipment scripts and examining test results.
The following list describes specific advantages associated with proof of concept testing
• Address any design concerns without affecting your production network
• Build and test configuration scripts before implementation
• Test new IOS, Cat OS and WAN OS versions and firmware
• Sell design feasibility to the client
Proof of Concept Model
The following numbered list describes all proof of concept components and specific sequence.
1. Prototype Design
2. Provision Equipment
3. Define Tests
4. Build Equipment Scripts
5. Review Test Results
Prototype Design
The prototype is a model for testing design and configuration features in a non-production setting such as a lab. You concern could be with specific protocols or IOS services and how they work with current protocols and IOS services running on your production network. The design should specify topology, equipment, addressing and software versions.
Provision Equipment
Obtain the circuits, cables, devices and servers required for testing. The equipment and software should be identical to the proposed design for specific testing and verification. Connect the equipment as specified with the prototype and make note of specific software versions and firmware being tested.
Define Tests
The tests should be designed to verify the design works as described at all Layers of the OSI model. That would focus on physical, network and application connectivity. The following is a suggested list that should be modified for your particular concerns. Depending on the current network and your tests, it could be an option to implement testing at some access offices with minimal impact on the production network.
The following is a list of typical tests that should be conducted
• Ping Equipment and Servers
• Routing and Switching
• Security Testing
• Availability Testing
• Application Load Testing
Build Equipment Scripts
Work with vendors to build the correct scripts for each device. This is particularly relevant if the design will utilize newer equipment and protocols that have yet to be standardized with the industry. Discuss any problems or concerns the vendor has with your current design and, if necessary, modify scripts and design specifics Review Test Results
The proof of concept test results should discuss specific issues with all defined tests. Note what problems were resolved and those that were referred to a vendor. The test results should be utilized to make changes to the current infrastructure, security and management specifications developed so far before moving on to the design proposal.
Network Planning and Design Guide is available at amazon.com and eBookmall.com
Shaun Hummel is an author of various technical books and has a web site focused on information technology job search solutions and certifications.
http://www.networkjobsolutions.com
About the Author
Shaun Hummel, CCNP, is a Senior Network Engineer with 11 years experience in enterprise network planning, design, and implementation. He has worked for various private and public companies in Canada and the United States improving infrastructure, security, and management. He has written Network Planning and Design Guide, Cisco Wireless Network Design Guide and Network Assessment Guide. www.networkjobsolutions.com
testing server load
How To Test Server Load Balancers--BreakingPoint Systems