Certified Wireless Network Administrator
The Certified Wireless Network Administrator (CWNA) is a foundation level certification that measures the ability to administer any wireless LAN. A wide range of topics focusing on the 802.11 wireless LAN technology are covered in the coursework and exam, which is vendor neutral.
•
Certification track
The CWNA is the second exam in a four-level certification process that narrows its scope and focus during each step. Topics progress from wireless fundamentals (at the Wireless# level), to the unique security requirements of 802.11 networks (CWSP), plus network & protocol analysis (at the CWNE level).
CWNA requirements
The main subject areas covered by the CWNA are as follows
• Radio Technologies
• Antenna Concepts
• Wireless LAN hardware and software
• Network Design Installation and Management
• Wireless Standards and Organisation
• 802.11 Network Architecture
• Wireless LAN Security
• Troubleshooting
• How to perform site surveys
These subjects are covered at an introductory level in the CWNA coursework and examination. The other certifications specialize in one or more of these subjects.
Recertification
The CWNA certification is valid for three years. The certification may be renewed by retaking the CWNA exam or by advancing on to the next level (CWSP), and then to CWNE which is a lifetime qualification (as of 1/1/07).
Saturday, May 29, 2010
Friday, May 21, 2010
What Is Windows Server Update Services (WSUS)?
What Is Windows Server Update Services (WSUS)?
________________________________________
This page provides an overview to Windows Server Update Services (WSUS), based on WSUS Release Candidate. For information on the new features in WSUS, see What's New In WSUS.
Index
• WSUS Overview
• WSUS Updates
• WSUS Database
• Client Targeting
• Update Approval
• Bandwidth Conservation
• Firewall Considerations
• IIS Considerations
• Mobile Clients
• Migration From SUS to WSUS
________________________________________
WSUS Overview
Windows Software Update Services (WSUS), is Microsoft's upcoming free patch management tool. WSUS is essentially the next version of Microsoft's free patch management tool, replacing Software Update Services or SUS. WSUS provides a number of new features including targeting of patches to specific groups of machines, support for more produts (e.g Office), and improved reporting.
In beta for over a year, RC of WSUS released on 22 March 2005. WSUS RTM is expected to be released during the first half of 2005 (e.g. by end June 2005). Service Pack1 for WSUS, which provides support for Windows Vista, new versions of the database and performance increases was released at the beginning of June 2006. More details on this release are available here. For more information on the background to WSUS and Microsoft's approach to patch management see WSUS Background.
WSUS is a service you run inside your organisation - on one or more servers which you configure to serve software updates to one or more AU clients. You can configure a WSUS server to download updates either from Microsoft or from another WSUS server within your organisation. Once you approve an update for installation, WSUS downloads it from configured upstream partner, and can then issue these updates to clients that request it. You can approve any update for some, all, or none of your computers. Once an update is approved, the targeted WSUS clients download the update using the Windows AU client. WSUS also provides reports on which clients have, and have not, had which updates.
WSUS provides a capability that allows the Windows AU client to obtain and install updates. However, it does not provide an internal version of the Windows Update site, thus your users can not navigate to your WSUS server and obtain updates (as they can when they navigate to Microsoft's Windows Update site).
You administer WSUS from the WSUS administration console: http://:/WsusAdmin/. On your WSUS server you can also click Start, point to All Programs, point to Administrative Tools, and then click Microsoft Windows Server Update Services. Note that if you do not add your WSUS administration Web site name to the list of sites in the Local Intranet zone in Internet Explorer, you might be prompted for credentials each time you open the WSUS administration console.
WSUS also supports the option to Allow local administrator to use the Automatic Updates control panel applet to select a configuration option of their choice. Note that Local Administrators are not allowed to disable Automatic Updates. The setting Allow local administrator to choose setting only appears if Automatic Updates has updated itself to the version compatible with WSUS.
Q: Where does this option appear?
WSUS Updates
As noted above, WSUS enables you to download updates from Microsoft and distribute these to your clients. There is no support in WSUS for adding additional updates, e.g. for updates to 3rd party or your own applications, etc.
For WSUS, Microsoft intent to provice several different levels of updates (from crticial security patches to updated drivers). Support is provided for some, but not all, Microsoft products. For details on what products and levels of update are supported see WSUS Supported Updates
WSUS Database
The WSUS service makes use use of an SQL database, which is either supported by SQL Server or by MSDE/WMSDE (see WSUS Database for more details on the WSUS Database). Each WSUS server requries a separate database, thus if you plan to suppor multiple WSUS servers in your environment, you need to support multiple WSUS databases. If you are installing WSUS on Windows Server 2003 operating system or later, you can install WMSDE included in WSUS Setup. If you are installing WSUS on Windows 2000 Server operating system, install the MSDE database software prior to installing WSUS.
The WSUS database stores the following types of information:
• WSUS server configuration information
• Metadata that describes each update
• Detailed Information about clients, updates, and client interaction with updates
The metadata for an update describes the update, lists the files required to install the update, and contains the relevant end user license agreement (EULA) for that update. Metadata is small, typically much smaller than the update itself, and is downloaded when you synchronise a WSUS server. An update, however, is only downloaded when it has been approved for installation.
Client Targeting
A key feature in WSUS is the ability to target updates to specific computers. WSUS enables you to create one or more target groups, to populate the target group with appropriate computers, and then approve updates for each target resume group independently. There are two default target groups All Computers and Unassigned Computers but you can add as many target groups as needed to support your approach to client targeting.
Update Approval
WSUS offers a number of features associated with approving updates, including setting deadlines for updates to be completed and uninstalling updates. A WSUS server first downloads download metadata, which allows the administrator to choose which updates to approve either for detection or installation. Updates can also be declined. The actual update is only downloaded to the WSUS server when you approve the update for installation.
Once you have approved update to members of one more Target group, computers belonging to the groups check in with the WSUS server and either check or deploy the approved updates. You can subsequently use WSUS reporting to determine the status of those updates.
For more informaiton on Update Approval, see Approve Updates.
Bandwidth Conservation
Updates distributed via WSUS can be very large (Windows XP SP2 for example is over 200 MB). WSUS attempts to be as bandwidth friendly as possible. First WSUS downloads update metadata. This is done independently of the update itself, which is downloaded only after it has been approved for installation.
And WSUS also provides supports servers that are not directly connected to the Internet. In this scenario, you first download updates to an Upstream server, then hand-carry media to disconnected servers running WSUS, and using the export/import feature to import the updates into your disconnected WSUS server.
For more information on how WSUS conserves bandwidth, see Bandwidth Considerations.
Firewall Considerations
If there is a firewall between the network you are running WSUS on and the Internet, you need to allow both HTTP and HTTPS traffic (port 80 for the HTTP protocol and port 443 for HTTPS) from your WSUS server to a limited set of sites, as follows:
• http://windowsupdate.microsoft.com
• http://*.windowsupdate.microsoft.com
• https://*.windowsupdate.microsoft.com
• http://download.windowsupdate.com
• http://*.download.windowsupdate.com
• http://*.windowsupdate.com
• http://wustat.windows.com
• http://ntservicepack.microsoft.com
Q: Where does this list come from? Is there a web link to this list that can be placed here to provide more authority?
A: see page 13 of Step-by-step guide to getting started with Microsoft Windows Update Services document from http://go.microsoft.com/fwlink?LinkId=39496
IIS Considerations
By default, WSUS installs into the default Web site in IIS (i.e on port 80). WSUS Setup gives you the option of creating a Web site on a custom port, the default being 8530. This allows you to run all WSUS traffic on a separate port, which may be helpful for internal firewalls.
During installation, WSUS stops, then starts the relevant web site. This includes the default default Web site if that was used. If you already have a Web site on the computer where you intend to install WSUS, use the setup option for creating a custom Web site. Note that if you install WSUS to port 8530, you have to manually set up the folder structure like, selfupdate virtual directory on port 80 to enable client self update using InstallSelfupdateOnPort80.vbs from installation folder.
Finally, ensure that the IWAM_ account is added to the Domain Administrators account on the WSUS Server. The IWAM account contains the ASPNET account used to start the WSUS service.
Mobile Clients
You can deploy an "internet facting" WSUS server outside your corporate firewall in order to distribute updates to mobile clients which are licensed to the same party as the WSUS server. See Implementing WSUS with ISA Server 2004 to manage remote clients white paper on Microsoft's WSUS TechNet site.
You can, of course, enable the clients to create a VPN into the corporate network, and once connected use your WSUS server to receive update approvals that are then downloaded either from your WSUS server for from Micrososft's servers.
Migration From SUS to WSUS
If you have already deployed SUS in your network, WSUS has a migration tool, Working with WSUSUTIL, that you can use to migrate approvals and updates from SUS to your WSUS server. This avoids re-downloading the patch content.
You cannot migrate any of the WSUS Service settings or IIS settings. Additionally, migration is a one-way process - you cannot migrate from WSUS to SUS. If you plan to install the WSUS server on a server already running SUS, then the WSUS installation process sets up WSUS to use an alternate port.>
________________________________________
This page provides an overview to Windows Server Update Services (WSUS), based on WSUS Release Candidate. For information on the new features in WSUS, see What's New In WSUS.
Index
• WSUS Overview
• WSUS Updates
• WSUS Database
• Client Targeting
• Update Approval
• Bandwidth Conservation
• Firewall Considerations
• IIS Considerations
• Mobile Clients
• Migration From SUS to WSUS
________________________________________
WSUS Overview
Windows Software Update Services (WSUS), is Microsoft's upcoming free patch management tool. WSUS is essentially the next version of Microsoft's free patch management tool, replacing Software Update Services or SUS. WSUS provides a number of new features including targeting of patches to specific groups of machines, support for more produts (e.g Office), and improved reporting.
In beta for over a year, RC of WSUS released on 22 March 2005. WSUS RTM is expected to be released during the first half of 2005 (e.g. by end June 2005). Service Pack1 for WSUS, which provides support for Windows Vista, new versions of the database and performance increases was released at the beginning of June 2006. More details on this release are available here. For more information on the background to WSUS and Microsoft's approach to patch management see WSUS Background.
WSUS is a service you run inside your organisation - on one or more servers which you configure to serve software updates to one or more AU clients. You can configure a WSUS server to download updates either from Microsoft or from another WSUS server within your organisation. Once you approve an update for installation, WSUS downloads it from configured upstream partner, and can then issue these updates to clients that request it. You can approve any update for some, all, or none of your computers. Once an update is approved, the targeted WSUS clients download the update using the Windows AU client. WSUS also provides reports on which clients have, and have not, had which updates.
WSUS provides a capability that allows the Windows AU client to obtain and install updates. However, it does not provide an internal version of the Windows Update site, thus your users can not navigate to your WSUS server and obtain updates (as they can when they navigate to Microsoft's Windows Update site).
You administer WSUS from the WSUS administration console: http://
WSUS also supports the option to Allow local administrator to use the Automatic Updates control panel applet to select a configuration option of their choice. Note that Local Administrators are not allowed to disable Automatic Updates. The setting Allow local administrator to choose setting only appears if Automatic Updates has updated itself to the version compatible with WSUS.
Q: Where does this option appear?
WSUS Updates
As noted above, WSUS enables you to download updates from Microsoft and distribute these to your clients. There is no support in WSUS for adding additional updates, e.g. for updates to 3rd party or your own applications, etc.
For WSUS, Microsoft intent to provice several different levels of updates (from crticial security patches to updated drivers). Support is provided for some, but not all, Microsoft products. For details on what products and levels of update are supported see WSUS Supported Updates
WSUS Database
The WSUS service makes use use of an SQL database, which is either supported by SQL Server or by MSDE/WMSDE (see WSUS Database for more details on the WSUS Database). Each WSUS server requries a separate database, thus if you plan to suppor multiple WSUS servers in your environment, you need to support multiple WSUS databases. If you are installing WSUS on Windows Server 2003 operating system or later, you can install WMSDE included in WSUS Setup. If you are installing WSUS on Windows 2000 Server operating system, install the MSDE database software prior to installing WSUS.
The WSUS database stores the following types of information:
• WSUS server configuration information
• Metadata that describes each update
• Detailed Information about clients, updates, and client interaction with updates
The metadata for an update describes the update, lists the files required to install the update, and contains the relevant end user license agreement (EULA) for that update. Metadata is small, typically much smaller than the update itself, and is downloaded when you synchronise a WSUS server. An update, however, is only downloaded when it has been approved for installation.
Client Targeting
A key feature in WSUS is the ability to target updates to specific computers. WSUS enables you to create one or more target groups, to populate the target group with appropriate computers, and then approve updates for each target resume group independently. There are two default target groups All Computers and Unassigned Computers but you can add as many target groups as needed to support your approach to client targeting.
Update Approval
WSUS offers a number of features associated with approving updates, including setting deadlines for updates to be completed and uninstalling updates. A WSUS server first downloads download metadata, which allows the administrator to choose which updates to approve either for detection or installation. Updates can also be declined. The actual update is only downloaded to the WSUS server when you approve the update for installation.
Once you have approved update to members of one more Target group, computers belonging to the groups check in with the WSUS server and either check or deploy the approved updates. You can subsequently use WSUS reporting to determine the status of those updates.
For more informaiton on Update Approval, see Approve Updates.
Bandwidth Conservation
Updates distributed via WSUS can be very large (Windows XP SP2 for example is over 200 MB). WSUS attempts to be as bandwidth friendly as possible. First WSUS downloads update metadata. This is done independently of the update itself, which is downloaded only after it has been approved for installation.
And WSUS also provides supports servers that are not directly connected to the Internet. In this scenario, you first download updates to an Upstream server, then hand-carry media to disconnected servers running WSUS, and using the export/import feature to import the updates into your disconnected WSUS server.
For more information on how WSUS conserves bandwidth, see Bandwidth Considerations.
Firewall Considerations
If there is a firewall between the network you are running WSUS on and the Internet, you need to allow both HTTP and HTTPS traffic (port 80 for the HTTP protocol and port 443 for HTTPS) from your WSUS server to a limited set of sites, as follows:
• http://windowsupdate.microsoft.com
• http://*.windowsupdate.microsoft.com
• https://*.windowsupdate.microsoft.com
• http://download.windowsupdate.com
• http://*.download.windowsupdate.com
• http://*.windowsupdate.com
• http://wustat.windows.com
• http://ntservicepack.microsoft.com
Q: Where does this list come from? Is there a web link to this list that can be placed here to provide more authority?
A: see page 13 of Step-by-step guide to getting started with Microsoft Windows Update Services document from http://go.microsoft.com/fwlink?LinkId=39496
IIS Considerations
By default, WSUS installs into the default Web site in IIS (i.e on port 80). WSUS Setup gives you the option of creating a Web site on a custom port, the default being 8530. This allows you to run all WSUS traffic on a separate port, which may be helpful for internal firewalls.
During installation, WSUS stops, then starts the relevant web site. This includes the default default Web site if that was used. If you already have a Web site on the computer where you intend to install WSUS, use the setup option for creating a custom Web site. Note that if you install WSUS to port 8530, you have to manually set up the folder structure like, selfupdate virtual directory on port 80 to enable client self update using InstallSelfupdateOnPort80.vbs from installation folder.
Finally, ensure that the IWAM_ account is added to the Domain Administrators account on the WSUS Server. The IWAM account contains the ASPNET account used to start the WSUS service.
Mobile Clients
You can deploy an "internet facting" WSUS server outside your corporate firewall in order to distribute updates to mobile clients which are licensed to the same party as the WSUS server. See Implementing WSUS with ISA Server 2004 to manage remote clients white paper on Microsoft's WSUS TechNet site.
You can, of course, enable the clients to create a VPN into the corporate network, and once connected use your WSUS server to receive update approvals that are then downloaded either from your WSUS server for from Micrososft's servers.
Migration From SUS to WSUS
If you have already deployed SUS in your network, WSUS has a migration tool, Working with WSUSUTIL, that you can use to migrate approvals and updates from SUS to your WSUS server. This avoids re-downloading the patch content.
You cannot migrate any of the WSUS Service settings or IIS settings. Additionally, migration is a one-way process - you cannot migrate from WSUS to SUS. If you plan to install the WSUS server on a server already running SUS, then the WSUS installation process sets up WSUS to use an alternate port.>
Wednesday, May 19, 2010
एथिकल एर्तिफ़िएद Hacker
Certified Ethical Hacker
The Certified Ethical Hacker (C|EH) is a professional certification provided by the International Council of E-Commerce Consultants (EC-Council.)
An Ethical Hacker is one name given to a Penetration Tester. An ethical hacker is usually employed by an organization who trusts him to attempt to penetrate networks and/or computer systems, using the same methods as a hacker, for the purpose of finding and fixing computer security vulnerabilities. Illegal hacking (i.e.; gaining unauthorized access to computer systems) is a crime in most countries, but penetration testing done by request of the owner of the targeted system(s) or network(s) is not, except in Germany.
A Certified Ethical Hacker has obtained a certification in how to look for the weaknesses and vulnerabilities in target systems and uses the same knowledge and tools as a hacker.
The certification is in Version 6 as of August 2008.
The EC-Council offers another certification, known as Certified Network Defense Architect (C|NDA). This certification is designed for United States Government Agencies, and is available only to members of selected agencies. Other than the name, the content of the course is exactly the same. The exam code for CNDA is 312-99.[1]
To get a more detailed understanding of this process see the Ethical Hack page.
•
Certification coursework
The coursework consists of 67 modules, which range from 30 minutes to five hours or more, depending on the depth of the information provided.
Some training centers and universities in Asia and Europe include EC Council's CEH program in one of their course modules.
Examination
Certification is achieved by taking the C|EH examination after having either attended training at an ATC (Accredited Training Center) or done self-study. If a candidate opts for self-study, an application must be filled out and proof submitted of 2 years of relevant information security work experience. In case you do not have two years of information security related work experience you can send them a request detailing your educational background and request for consideration on a case basis.[2] The current version of the CEH, v6, uses EC-Council's exam 312-50, as did v5. This exam has 150 multiple-choice questions and a 4 hour time limit. The earlier v4 had 125 multiple-choice questions and a three hour time limit. The exam costs US$250 in the United States (prices in other countries may differ)[3], and is administered via computer at an EC-Council Accredited Training Center, Pearson VUE, or Prometric testing center (in the United States).
Recertification
EC-Council Continuing Education (ECE) points serve to ensure that all certified professionals maintain and further their knowledge. Professionals must meet ECE requirements to avoid revocation of certification. Members holding the C|EH/CNDA designation (as well as other EC-Council certifications) must recertify under this program every three years for a minimum of 120 credits (20 credits per year).
Controversy
Certain computer security professionals, such as Marcus J. Ranum, have objected to the term ethical hacker: "There's no such thing as an 'ethical hacker' - that's like saying 'ethical rapist' - it's a contradiction in terms."[4] Part of the controversy may arise from the older, less stigmatized, definition of hacker, which has become synonymous with computer criminal.
On the other hand, some companies do not seem to mind the association. According to EC-Council, there has been an increase of careers where CEH and other ethical hacking certifications are preferred or required.[5][6][7]
Further reading
• Graves, Kimberly; CEH Certified Ethical Hacker Study Guide, Wiley, John & Sons, Incorporated, 2010. ISBN 978-0470525207
• Graves, Kimberly; Official Certified Ethical Hacker Review Guide, Sybex Publishing, 2006. ISBN 978-0782144376
• Gregg, Michael; Certified Ethical Hacker Exam Prep, Que Publishing, 2006.
The Certified Ethical Hacker (C|EH) is a professional certification provided by the International Council of E-Commerce Consultants (EC-Council.)
An Ethical Hacker is one name given to a Penetration Tester. An ethical hacker is usually employed by an organization who trusts him to attempt to penetrate networks and/or computer systems, using the same methods as a hacker, for the purpose of finding and fixing computer security vulnerabilities. Illegal hacking (i.e.; gaining unauthorized access to computer systems) is a crime in most countries, but penetration testing done by request of the owner of the targeted system(s) or network(s) is not, except in Germany.
A Certified Ethical Hacker has obtained a certification in how to look for the weaknesses and vulnerabilities in target systems and uses the same knowledge and tools as a hacker.
The certification is in Version 6 as of August 2008.
The EC-Council offers another certification, known as Certified Network Defense Architect (C|NDA). This certification is designed for United States Government Agencies, and is available only to members of selected agencies. Other than the name, the content of the course is exactly the same. The exam code for CNDA is 312-99.[1]
To get a more detailed understanding of this process see the Ethical Hack page.
•
Certification coursework
The coursework consists of 67 modules, which range from 30 minutes to five hours or more, depending on the depth of the information provided.
Some training centers and universities in Asia and Europe include EC Council's CEH program in one of their course modules.
Examination
Certification is achieved by taking the C|EH examination after having either attended training at an ATC (Accredited Training Center) or done self-study. If a candidate opts for self-study, an application must be filled out and proof submitted of 2 years of relevant information security work experience. In case you do not have two years of information security related work experience you can send them a request detailing your educational background and request for consideration on a case basis.[2] The current version of the CEH, v6, uses EC-Council's exam 312-50, as did v5. This exam has 150 multiple-choice questions and a 4 hour time limit. The earlier v4 had 125 multiple-choice questions and a three hour time limit. The exam costs US$250 in the United States (prices in other countries may differ)[3], and is administered via computer at an EC-Council Accredited Training Center, Pearson VUE, or Prometric testing center (in the United States).
Recertification
EC-Council Continuing Education (ECE) points serve to ensure that all certified professionals maintain and further their knowledge. Professionals must meet ECE requirements to avoid revocation of certification. Members holding the C|EH/CNDA designation (as well as other EC-Council certifications) must recertify under this program every three years for a minimum of 120 credits (20 credits per year).
Controversy
Certain computer security professionals, such as Marcus J. Ranum, have objected to the term ethical hacker: "There's no such thing as an 'ethical hacker' - that's like saying 'ethical rapist' - it's a contradiction in terms."[4] Part of the controversy may arise from the older, less stigmatized, definition of hacker, which has become synonymous with computer criminal.
On the other hand, some companies do not seem to mind the association. According to EC-Council, there has been an increase of careers where CEH and other ethical hacking certifications are preferred or required.[5][6][7]
Further reading
• Graves, Kimberly; CEH Certified Ethical Hacker Study Guide, Wiley, John & Sons, Incorporated, 2010. ISBN 978-0470525207
• Graves, Kimberly; Official Certified Ethical Hacker Review Guide, Sybex Publishing, 2006. ISBN 978-0782144376
• Gregg, Michael; Certified Ethical Hacker Exam Prep, Que Publishing, 2006.
MCITP Success - Pursuing Microsoft Certifications
Microsoft has released some news on SQL Server 2008 certifications. In short, they'll be releasing three MCTS certifications this year based on three roles. Each role will require one exam to earn the MCTS certification.
• Database Administrator
• Database Developer
• Business Intelligence Developer
There will also be three MCITP tracks geared to the same three roles. The SQL 2008 MCITP tracks arent' decided yet and probably won't come out until about six months after SQL Server 2008 goes live (Q3 2008).
The three MCTS Certifications will be:
1. 70-432
MCTS: SQL Server 2008, Implementation and Maintenance
Role: Database Administrator
Expected go live date: August 2008
Beta target: June 2008
Focused on Database Admin role, unlike the 70-431 exam which covers multiple roles
Test topics ():
- Installing and configuring
- Maintaining SQL Instances
- Managing Security
- Maintaining a database
- Data Management Tasks
- Monitoring and Troubleshooting
- Optimizing
- Implementing High Availability
2. 70-433
MCTS: SQL Server 2008, Database Development
Role: Database Developer
Expected go live date: September 2008
Beta target: July 2008
Test topics (not complete yet):
- T-SQL (triggers, stored procedures, views)
- Connecting to Datasources
3. 70-448
MCTS: SQL Server 2008, Business Intelligence Development and Maintenance
Role: Business Intelligence Developer
Expected go live date: August 2008
Beta target: June 2008
Test topics (not complete yet, similar to 70-445):
- Configuring, deploying, maintaining, and implementing
- SSIS
- SSRS
- SSAS
• Database Administrator
• Database Developer
• Business Intelligence Developer
There will also be three MCITP tracks geared to the same three roles. The SQL 2008 MCITP tracks arent' decided yet and probably won't come out until about six months after SQL Server 2008 goes live (Q3 2008).
The three MCTS Certifications will be:
1. 70-432
MCTS: SQL Server 2008, Implementation and Maintenance
Role: Database Administrator
Expected go live date: August 2008
Beta target: June 2008
Focused on Database Admin role, unlike the 70-431 exam which covers multiple roles
Test topics ():
- Installing and configuring
- Maintaining SQL Instances
- Managing Security
- Maintaining a database
- Data Management Tasks
- Monitoring and Troubleshooting
- Optimizing
- Implementing High Availability
2. 70-433
MCTS: SQL Server 2008, Database Development
Role: Database Developer
Expected go live date: September 2008
Beta target: July 2008
Test topics (not complete yet):
- T-SQL (triggers, stored procedures, views)
- Connecting to Datasources
3. 70-448
MCTS: SQL Server 2008, Business Intelligence Development and Maintenance
Role: Business Intelligence Developer
Expected go live date: August 2008
Beta target: June 2008
Test topics (not complete yet, similar to 70-445):
- Configuring, deploying, maintaining, and implementing
- SSIS
- SSRS
- SSAS
Subscribe to:
Posts (Atom)