- Microsoft lays out SQL Server road map
- Credit card skimming
- Nortel's stock market capitalization plummets
- The Obama campaign's Search Engine to Nowhere
- Will Apple be forced to make more money?
Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:Application Performance Solutions | App Performance | Networking Solution | SafeGuard Enterprise Solution Center | SOA | Test your Web Filter | Value of WDS
EXCLUSIVE FREE BOOK CHAPTERS
Welcome to Microsoft Subnet's Pearson Education page -- your access to free and exclusive chapters of new and classic Pearson Education books about Microsoft technologies. Every month we hold book giveaway competitions so check this page often. To enter to win this month's book giveaway click here.
| Published by Que ISBN-10: 0-7897-3777-9 ISBN-13: 978-0-7897-3777-9 |
|
Chapter 8: Accessing and Sharing Network Resources
In this chapter
Accessing Shared Network Resources
Mapping a Network Folder to a Local Drive Letter
Creating a Network Location for a Remote Folder
Accessing a Shared Printer
Sharing Resources with the Network
Many home and small office networks exist for no other reason than to share a broadband Internet connection. The administrators of those networks attach a broadband modem to a router, configure the router, run some ethernet cable (or set up wireless connections), and then they never think about the network again.
There’s nothing wrong with this scenario, of course, but there’s something that just feels, well, incomplete about such a network. Sharing an Internet connection is a must for any modern network, but networking should be about sharing so much more: disk drives, folders, documents, music, photos, videos, recorded TV shows, printers, scanners, CD and DVD burners, projectors, and more.
This expanded view of networking is about working, playing, and connecting with your fellow network users. It is, in short, about sharing, and sharing is the subject of this chapter. You learn how to access those network resources that others have shared, and you learn how to share your own resources with the network.
| Published by Addison-Wesley Professional ISBN-10: 0-321-42345-3 ISBN-13: 978-0-321-42345-0 |
|
All About Execution
Creating the Baselines
Getting into a Rhythm
Quality Audits
Teaming
Politics
Summary
Case Study
This chapter is all about what has to be done when you execute your project. It seems pretty straightforward that your team will be performing the tasks of the project. But you will be amazed by all the activities that need to be done while those tasks are being performed. One of the activities that you might not be familiar with is the concept of quality audits. I introduce that concept in this chapter and talk about what gets audited. I also cover the subject of how many quality audits you might consider on your project. I finish that topic with the timings of quality audits.
First, though, you have to set up a baseline. I talk about each type of baseline and then cover how to use them and the purpose of baselining in general. Next comes the idea of getting into a rhythm on your project.
In "Teaming" I talk about another element to use to develop the project team: training. Team members will not perform effectively if they are not trained to do the job properly. I cover the different types of training that might be needed.
In "Politics" I talk about obstacles to executive communication. You might run into a couple executive types you have dealt with before: the Mad Hatter and the Executive Ostrich.
In the case study, Chris spends most of her week getting ready for the meeting with June. She still has to complete the budget and the schedule to properly brief June. She gets caught up in a lot of meetings, though, and has a lot of details to work through to finish in time.
Actions
Activities
History
Notes
Attachments
Run Workflow
Advanced Find
Form Assistant
Record Merge
Send Direct E-mail
Resource Center
Microsoft Dynamics CRM has a number of common features. By "common," we mean that, when working with most of the entities, they have the same functionality included in this chapter.
As an example, Accounts, Contacts, Leads, Opportunities, and Cases all have functionality on their main form that includes the following:
Actions
Activities
History
Notes
Attachments
Workflows
Because they are so similar (regardless of which entity you're working with), we have grouped these functions in this chapter to consolidate the description of their functionality.
The Resource Center is included with this chapter because all users of the application use it in the same manner.
READ THE FULL CHAPTER.
Comment