Archive for the ‘Progamming’ Category

While in 1990th we saw very fierce fighting between Microsoft Windows and Apple Computer PowerMac for the workstations market, when two systems were practically not compatible and didn’t have plans to understand each other, plus all the blends of Unix/Linux were trying to step in and take workstation market over, the next decade in our opinion will be the decade of coexistence, integration, cross-platform heterogeneous data distribution and querying. Good example would be this – imagine you are freight forwarder and your company has Microsoft Business Solutions Great Plains implemented as accounting and partly distribution application and on the other hand you have Oracle based cargo delivery / tracking system. You do not have to phase out one or the other – you make them coexist: if you need Great Plains user to lookup shipment status – you use heterogeneous query from MS SQL Server (Great Plains) to Oracle via linked server and have instant result set on the screen. Similar heterogeneous query you can have from Oracle side to MS SQL Server. Let’s look at the trends:

o XML – is platform independent way to communicate: transfer inbound/outbound streams of data. This is the sign of future coexistence and it is very simple in reading and understanding by human being

o IT Budget. Evolution versus Revolution: the old days of restructuring your company business operation around new computer system are probably over. Nowadays IT budget is pretty limited and corporate management considers IT as regular (not elite) internal services department. So – you, as IT manager or director has limited resources to revolutionize the company, so you follow the step-by-step evolution

o The sunset of proprietary languages. Good example is Great Plains Dexterity – this is the core of recent Microsoft Great Plains, former Great Plains Dynamics. Dexterity had the history of evolution, and now it is using SQL Stored procs to do the majority of database querying and updating, Microsoft plans to phase it slowly out and replace with the future .Net language of choice (not sure which one will win: C# or VB.Net – but this is not important at this moment). In the close future SQL with XML inbound/outbound will be the language of integrations

o The end of heavy custom programming. At least in the US – majority of the project will be outsourced. In the USA we will be mostly dealing with project management and specifications writing, plus physical hardware support. Even if you are dealing with, say Microsoft Business Solutions partner in San Francisco – partner itself will be using either overseas facility or simply contractors over there. When the majority of us will become project managers, thinking about business logic, not the way of realizing it in the code – we will stop heating the opposite platform -no more Microsoft VB.Net programmer hatred toward Java/EJB/J2EE programmer

We are already doing cross platform integrations from Microsoft Business Solutions products: Microsoft CRM, Great Plains to Oracle, DB2, Lotus and other databases, plus Microsoft CRM email messaging through Lotus Domino to begin realize the strategy

Andrew Karasev is Chief Technology Officer in Alba Spectrum Technologies USA nationwide Great Plains, Microsoft CRM customization company, serving clients in Chicago, California, Texas, Florida, New York, Georgia, Arizona, Minnesota, UK, Australia and having locations in multiple states and internationally ( http://www.albaspectrum.com ), he is CMA, Great Plains Certified Master, Dexterity, SQL, C#.Net, Crystal Reports and Microsoft CRM SDK developer.

Author: Andrew Karasev
Article Source: EzineArticles.com
Provided by: Digital Camera Information

Because of the complexity of Microsoft Exchange Server management and administration, many companies want to consolidate thousands of Exchange users on one server. As a deployment grows, its increasing number of servers can make administrative tasks such as adding, moving, and deleting users extremely time-consuming for Exchange administrators. Administrators must use a combination of applications to administer and manage the Exchange environment, which makes administration of large implementations more difficult. Future versions of Exchange Server will simplify some of these management and administrative tasks and will enable administrators to perform all Exchange administrative tasks through one application. However, for now, Exchange Server’s diversity of tasks and tools leads many companies to want to consolidate as many users as possible on each Exchange Server machine.

Microsoft has been using the Security Development Life cycle (SDL) across its product lines for several years now, and we’ve seen an across-the-board improvement in product security as a result. As a security practitioner, this situation makes me happy indeed, but as an Exchange Server administrator, I want functional improvements to the product as well. Given that Microsoft is already actively working on the next version of Exchange, I wanted to set down a few things I’d like to see in the Exchange Server of the future.

Keep in mind that for every feature we get, there are other features that don’t make the cut. Even with the company’s massive resources behind them, Microsoft’s developers have constraints that prevent them from adding every desired feature while still meeting their schedules and deadlines. That said, here are a few items from my wish list for the next Exchange release.

Let’s start with a relatively easy one: The next version of Exchange should include full support for Outlook Web Access’ premium mode in Firefox and Safari. Multiple-browser support is an important check box for the education market (where you’re likely to find more people using non-Microsoft Internet Explorer browsers), but it’s also something that I would expect to see from the company that pioneered the commercial use of Asynchronous JavaScript and XML (Ajax) in Web applications–not to mention that Microsoft Office Communicator Web Access and all of IBM’s Lotus products already fully support these browsers.

How about certificates? Microsoft Exchange Server has a Certificate Wizard that helps you get the right set of machine names and subject alternative names in your certificate requests. Now that the OCS and Exchange product lines are part of the same business unit within Microsoft, perhaps the two teams could collaborate to produce a single certificate tool that collects all the necessary parameters for certificate requests? Network security and Exchange administrators everywhere would greatly appreciate and benefit from such a feature.

I’ve heard many requests for running Exchange services on Windows Server Core, the bare bones install option with Windows Server 2008; the obstacle here is that the current version of Windows Power Shell won’t run on Server Core. The Windows or Power Shell teams might address this problem on their own; personally, I’d rather they spent their engineering efforts on giving us complete support for running Exchange under Hyper-V.

Nina Swadie is an Online Small Business Support Executive for iYogi who provides detailed information on Online Server Support, in Small Business Server Support, Exchange Server Support, Terminal Server Support, Windows 2000 & 2003 Server, in Server Support, Small business technical support and Windows Server Support etc.

Author: Nina Swadie
Article Source: EzineArticles.com
Provided by: Digital Camera Times

Because of the complexity of Microsoft Exchange Server management and administration, many companies want to consolidate thousands of Exchange users on one server. As a deployment grows, its increasing number of servers can make administrative tasks such as adding, moving, and deleting users extremely time-consuming for Exchange administrators. Administrators must use a combination of applications to administer and manage the Exchange environment, which makes administration of large implementations more difficult. Future versions of Exchange Server will simplify some of these management and administrative tasks and will enable administrators to perform all Exchange administrative tasks through one application. However, for now, Exchange Server’s diversity of tasks and tools leads many companies to want to consolidate as many users as possible on each Exchange Server machine.

Microsoft has been using the Security Development Life cycle (SDL) across its product lines for several years now, and we’ve seen an across-the-board improvement in product security as a result. As a security practitioner, this situation makes me happy indeed, but as an Exchange Server administrator, I want functional improvements to the product as well. Given that Microsoft is already actively working on the next version of Exchange, I wanted to set down a few things I’d like to see in the Exchange Server of the future.

Keep in mind that for every feature we get, there are other features that don’t make the cut. Even with the company’s massive resources behind them, Microsoft’s developers have constraints that prevent them from adding every desired feature while still meeting their schedules and deadlines. That said, here are a few items from my wish list for the next Exchange release.

Let’s start with a relatively easy one: The next version of Exchange should include full support for Outlook Web Access’ premium mode in Firefox and Safari. Multiple-browser support is an important check box for the education market (where you’re likely to find more people using non-Microsoft Internet Explorer browsers), but it’s also something that I would expect to see from the company that pioneered the commercial use of Asynchronous JavaScript and XML (Ajax) in Web applications–not to mention that Microsoft Office Communicator Web Access and all of IBM’s Lotus products already fully support these browsers.

How about certificates? Microsoft Exchange Server has a Certificate Wizard that helps you get the right set of machine names and subject alternative names in your certificate requests. Now that the OCS and Exchange product lines are part of the same business unit within Microsoft, perhaps the two teams could collaborate to produce a single certificate tool that collects all the necessary parameters for certificate requests? Network security and Exchange administrators everywhere would greatly appreciate and benefit from such a feature.

I’ve heard many requests for running Exchange services on Windows Server Core, the bare bones install option with Windows Server 2008; the obstacle here is that the current version of Windows Power Shell won’t run on Server Core. The Windows or Power Shell teams might address this problem on their own; personally, I’d rather they spent their engineering efforts on giving us complete support for running Exchange under Hyper-V.

Nina Swadie is an Online Small Business Support Executive for iYogi who provides detailed information on Online Server Support, in Small Business Server Support, Exchange Server Support, Terminal Server Support, Windows 2000 & 2003 Server, in Server Support, Small business technical support and Windows Server Support etc.

Author: Nina Swadie
Article Source: EzineArticles.com
Provided by: US Dollar credit card

Because of the complexity of Microsoft Exchange Server management and administration, many companies want to consolidate thousands of Exchange users on one server. As a deployment grows, its increasing number of servers can make administrative tasks such as adding, moving, and deleting users extremely time-consuming for Exchange administrators. Administrators must use a combination of applications to administer and manage the Exchange environment, which makes administration of large implementations more difficult. Future versions of Exchange Server will simplify some of these management and administrative tasks and will enable administrators to perform all Exchange administrative tasks through one application. However, for now, Exchange Server’s diversity of tasks and tools leads many companies to want to consolidate as many users as possible on each Exchange Server machine.

Microsoft has been using the Security Development Life cycle (SDL) across its product lines for several years now, and we’ve seen an across-the-board improvement in product security as a result. As a security practitioner, this situation makes me happy indeed, but as an Exchange Server administrator, I want functional improvements to the product as well. Given that Microsoft is already actively working on the next version of Exchange, I wanted to set down a few things I’d like to see in the Exchange Server of the future.

Keep in mind that for every feature we get, there are other features that don’t make the cut. Even with the company’s massive resources behind them, Microsoft’s developers have constraints that prevent them from adding every desired feature while still meeting their schedules and deadlines. That said, here are a few items from my wish list for the next Exchange release.

Let’s start with a relatively easy one: The next version of Exchange should include full support for Outlook Web Access’ premium mode in Firefox and Safari. Multiple-browser support is an important check box for the education market (where you’re likely to find more people using non-Microsoft Internet Explorer browsers), but it’s also something that I would expect to see from the company that pioneered the commercial use of Asynchronous JavaScript and XML (Ajax) in Web applications–not to mention that Microsoft Office Communicator Web Access and all of IBM’s Lotus products already fully support these browsers.

How about certificates? Microsoft Exchange Server has a Certificate Wizard that helps you get the right set of machine names and subject alternative names in your certificate requests. Now that the OCS and Exchange product lines are part of the same business unit within Microsoft, perhaps the two teams could collaborate to produce a single certificate tool that collects all the necessary parameters for certificate requests? Network security and Exchange administrators everywhere would greatly appreciate and benefit from such a feature.

I’ve heard many requests for running Exchange services on Windows Server Core, the bare bones install option with Windows Server 2008; the obstacle here is that the current version of Windows Power Shell won’t run on Server Core. The Windows or Power Shell teams might address this problem on their own; personally, I’d rather they spent their engineering efforts on giving us complete support for running Exchange under Hyper-V.

Nina Swadie is an Online Small Business Support Executive for iYogi who provides detailed information on Online Server Support, in Small Business Server Support, Exchange Server Support, Terminal Server Support, Windows 2000 & 2003 Server, in Server Support, Small business technical support and Windows Server Support etc.

Author: Nina Swadie
Article Source: EzineArticles.com
Provided by: Canada duty

While in 1990th we saw very fierce fighting between Microsoft Windows and Apple Computer PowerMac for the workstations market, when two systems were practically not compatible and didn’t have plans to understand each other, plus all the blends of Unix/Linux were trying to step in and take workstation market over, the next decade in our opinion will be the decade of coexistence, integration, cross-platform heterogeneous data distribution and querying. Good example would be this – imagine you are freight forwarder and your company has Microsoft Business Solutions Great Plains implemented as accounting and partly distribution application and on the other hand you have Oracle based cargo delivery / tracking system. You do not have to phase out one or the other – you make them coexist: if you need Great Plains user to lookup shipment status – you use heterogeneous query from MS SQL Server (Great Plains) to Oracle via linked server and have instant result set on the screen. Similar heterogeneous query you can have from Oracle side to MS SQL Server. Let’s look at the trends:

o XML – is platform independent way to communicate: transfer inbound/outbound streams of data. This is the sign of future coexistence and it is very simple in reading and understanding by human being

o IT Budget. Evolution versus Revolution: the old days of restructuring your company business operation around new computer system are probably over. Nowadays IT budget is pretty limited and corporate management considers IT as regular (not elite) internal services department. So – you, as IT manager or director has limited resources to revolutionize the company, so you follow the step-by-step evolution

o The sunset of proprietary languages. Good example is Great Plains Dexterity – this is the core of recent Microsoft Great Plains, former Great Plains Dynamics. Dexterity had the history of evolution, and now it is using SQL Stored procs to do the majority of database querying and updating, Microsoft plans to phase it slowly out and replace with the future .Net language of choice (not sure which one will win: C# or VB.Net – but this is not important at this moment). In the close future SQL with XML inbound/outbound will be the language of integrations

o The end of heavy custom programming. At least in the US – majority of the project will be outsourced. In the USA we will be mostly dealing with project management and specifications writing, plus physical hardware support. Even if you are dealing with, say Microsoft Business Solutions partner in San Francisco – partner itself will be using either overseas facility or simply contractors over there. When the majority of us will become project managers, thinking about business logic, not the way of realizing it in the code – we will stop heating the opposite platform -no more Microsoft VB.Net programmer hatred toward Java/EJB/J2EE programmer

We are already doing cross platform integrations from Microsoft Business Solutions products: Microsoft CRM, Great Plains to Oracle, DB2, Lotus and other databases, plus Microsoft CRM email messaging through Lotus Domino to begin realize the strategy

Andrew Karasev is Chief Technology Officer in Alba Spectrum Technologies USA nationwide Great Plains, Microsoft CRM customization company, serving clients in Chicago, California, Texas, Florida, New York, Georgia, Arizona, Minnesota, UK, Australia and having locations in multiple states and internationally ( http://www.albaspectrum.com ), he is CMA, Great Plains Certified Master, Dexterity, SQL, C#.Net, Crystal Reports and Microsoft CRM SDK developer.

Author: Andrew Karasev
Article Source: EzineArticles.com
Provided by: Excise Tax

While in 1990th we saw very fierce fighting between Microsoft Windows and Apple Computer PowerMac for the workstations market, when two systems were practically not compatible and didn’t have plans to understand each other, plus all the blends of Unix/Linux were trying to step in and take workstation market over, the next decade in our opinion will be the decade of coexistence, integration, cross-platform heterogeneous data distribution and querying. Good example would be this – imagine you are freight forwarder and your company has Microsoft Business Solutions Great Plains implemented as accounting and partly distribution application and on the other hand you have Oracle based cargo delivery / tracking system. You do not have to phase out one or the other – you make them coexist: if you need Great Plains user to lookup shipment status – you use heterogeneous query from MS SQL Server (Great Plains) to Oracle via linked server and have instant result set on the screen. Similar heterogeneous query you can have from Oracle side to MS SQL Server. Let’s look at the trends:

o XML – is platform independent way to communicate: transfer inbound/outbound streams of data. This is the sign of future coexistence and it is very simple in reading and understanding by human being

o IT Budget. Evolution versus Revolution: the old days of restructuring your company business operation around new computer system are probably over. Nowadays IT budget is pretty limited and corporate management considers IT as regular (not elite) internal services department. So – you, as IT manager or director has limited resources to revolutionize the company, so you follow the step-by-step evolution

o The sunset of proprietary languages. Good example is Great Plains Dexterity – this is the core of recent Microsoft Great Plains, former Great Plains Dynamics. Dexterity had the history of evolution, and now it is using SQL Stored procs to do the majority of database querying and updating, Microsoft plans to phase it slowly out and replace with the future .Net language of choice (not sure which one will win: C# or VB.Net – but this is not important at this moment). In the close future SQL with XML inbound/outbound will be the language of integrations

o The end of heavy custom programming. At least in the US – majority of the project will be outsourced. In the USA we will be mostly dealing with project management and specifications writing, plus physical hardware support. Even if you are dealing with, say Microsoft Business Solutions partner in San Francisco – partner itself will be using either overseas facility or simply contractors over there. When the majority of us will become project managers, thinking about business logic, not the way of realizing it in the code – we will stop heating the opposite platform -no more Microsoft VB.Net programmer hatred toward Java/EJB/J2EE programmer

We are already doing cross platform integrations from Microsoft Business Solutions products: Microsoft CRM, Great Plains to Oracle, DB2, Lotus and other databases, plus Microsoft CRM email messaging through Lotus Domino to begin realize the strategy

Andrew Karasev is Chief Technology Officer in Alba Spectrum Technologies USA nationwide Great Plains, Microsoft CRM customization company, serving clients in Chicago, California, Texas, Florida, New York, Georgia, Arizona, Minnesota, UK, Australia and having locations in multiple states and internationally ( http://www.albaspectrum.com ), he is CMA, Great Plains Certified Master, Dexterity, SQL, C#.Net, Crystal Reports and Microsoft CRM SDK developer.

Author: Andrew Karasev
Article Source: EzineArticles.com
Provided by: Import duty tariff

Play framework is a full stack web framework for Java. Play focuses on programmers targets and productivity. It is an excellent companion for disciplined project management process. It’s aim is to lighten web applications development as long as attach with Java. Its best feature is that the code changes are identified and reloaded by the development web server. Play is a perfect Java framework. It allows you to manage your favorite libraries and development tools.

Fix the bug and hit Reload

The framework compiles the Java source codes and reloads them into the JVM directly. You can then edit, reload and see the modifications immediately, without the need to restart the server. So if you want, you can skip a full-featured Java IDE and work with a simple text editor. When an error occurs, the framework recognize it and shows the problem. Even the stack traces are displayed down and it makes easier to resolve the problems.

Simple stateless MVC architecture

Component based and state full Java Web framework can save page state automatically, but it has lot of other difficulties like if the user opens a second window or hits the browser back button.

As the browser developed into more powerful, this is the best option to use offline storage or Ajax to resolve the client-side state problems.

HTTP-to-code mapping

A Web application framework should provide you straightforward,full access to HTTP and its concepts, which is the main difference between other Java web application frameworks and Play. And the Request/Response pattern, HTTP, content-type negotiation, the REST architectural style, URI are all important ideas for the play framework.

Efficient template engine

The template system of Play is very efficient which allows to generate HTML, XML, JSON or any text based format document dynamically. The expression language of the template engine is Groovy. To create re-usable functions, you can use a tag system. All the Templates are saved in the directory – app/views.

JPA with Play

JPA (The Java Persistence Architecture) is the finest Object Relational Mapping API applicable for Java. If you are familiar with JPA, it will be very simpler with Play. No configuration is needed, the framework will start the Entity Manager of JPA automatically and when the code is reloaded, it synchronizes marvelously. In addition, if you use the superclass play.db.jpa.Model it will help in making your code attractive.

Test driven development

To make your application very powerful, it is a good way to create automatic test suites. It provides you to work in a very active way. Depending on what you need to test, the play framework tests are set up using Selenium or Junit 4. All kinds of tests can be written, from full acceptance tests to simple unit tests and can run them directly using Selenium in a browser.

Full-stack application framework

The initial inspiration of the play framework was our own Java applications and it has all the components required to build a modern web application such as, relational database support through JDBC, Hibernate (with JPA API) to remain your Java objects in the Database, Integrated Cache support, Direct Web services utilization either in XML or JSON, Image manipulation API, OpenID support used for distributed authentication.

The modular architecture of play framework allows you to integrate a web application with many others. So you can reuse your java code, static resources like Javascript and CSS files and templates in an easy way.

Julian is a professional content writer on Java Development and now working at Telious Technologies.

Author: Julian Jaic
Article Source: EzineArticles.com
Provided by: Benefits of electric pressure cooker

Because of the complexity of Microsoft Exchange Server management and administration, many companies want to consolidate thousands of Exchange users on one server. As a deployment grows, its increasing number of servers can make administrative tasks such as adding, moving, and deleting users extremely time-consuming for Exchange administrators. Administrators must use a combination of applications to administer and manage the Exchange environment, which makes administration of large implementations more difficult. Future versions of Exchange Server will simplify some of these management and administrative tasks and will enable administrators to perform all Exchange administrative tasks through one application. However, for now, Exchange Server’s diversity of tasks and tools leads many companies to want to consolidate as many users as possible on each Exchange Server machine.

Microsoft has been using the Security Development Life cycle (SDL) across its product lines for several years now, and we’ve seen an across-the-board improvement in product security as a result. As a security practitioner, this situation makes me happy indeed, but as an Exchange Server administrator, I want functional improvements to the product as well. Given that Microsoft is already actively working on the next version of Exchange, I wanted to set down a few things I’d like to see in the Exchange Server of the future.

Keep in mind that for every feature we get, there are other features that don’t make the cut. Even with the company’s massive resources behind them, Microsoft’s developers have constraints that prevent them from adding every desired feature while still meeting their schedules and deadlines. That said, here are a few items from my wish list for the next Exchange release.

Let’s start with a relatively easy one: The next version of Exchange should include full support for Outlook Web Access’ premium mode in Firefox and Safari. Multiple-browser support is an important check box for the education market (where you’re likely to find more people using non-Microsoft Internet Explorer browsers), but it’s also something that I would expect to see from the company that pioneered the commercial use of Asynchronous JavaScript and XML (Ajax) in Web applications–not to mention that Microsoft Office Communicator Web Access and all of IBM’s Lotus products already fully support these browsers.

How about certificates? Microsoft Exchange Server has a Certificate Wizard that helps you get the right set of machine names and subject alternative names in your certificate requests. Now that the OCS and Exchange product lines are part of the same business unit within Microsoft, perhaps the two teams could collaborate to produce a single certificate tool that collects all the necessary parameters for certificate requests? Network security and Exchange administrators everywhere would greatly appreciate and benefit from such a feature.

I’ve heard many requests for running Exchange services on Windows Server Core, the bare bones install option with Windows Server 2008; the obstacle here is that the current version of Windows Power Shell won’t run on Server Core. The Windows or Power Shell teams might address this problem on their own; personally, I’d rather they spent their engineering efforts on giving us complete support for running Exchange under Hyper-V.

Nina Swadie is an Online Small Business Support Executive for iYogi who provides detailed information on Online Server Support, in Small Business Server Support, Exchange Server Support, Terminal Server Support, Windows 2000 & 2003 Server, in Server Support, Small business technical support and Windows Server Support etc.

Author: Nina Swadie
Article Source: EzineArticles.com
Provided by: Programmable pressure cooker

While in 1990th we saw very fierce fighting between Microsoft Windows and Apple Computer PowerMac for the workstations market, when two systems were practically not compatible and didn’t have plans to understand each other, plus all the blends of Unix/Linux were trying to step in and take workstation market over, the next decade in our opinion will be the decade of coexistence, integration, cross-platform heterogeneous data distribution and querying. Good example would be this – imagine you are freight forwarder and your company has Microsoft Business Solutions Great Plains implemented as accounting and partly distribution application and on the other hand you have Oracle based cargo delivery / tracking system. You do not have to phase out one or the other – you make them coexist: if you need Great Plains user to lookup shipment status – you use heterogeneous query from MS SQL Server (Great Plains) to Oracle via linked server and have instant result set on the screen. Similar heterogeneous query you can have from Oracle side to MS SQL Server. Let’s look at the trends:

o XML – is platform independent way to communicate: transfer inbound/outbound streams of data. This is the sign of future coexistence and it is very simple in reading and understanding by human being

o IT Budget. Evolution versus Revolution: the old days of restructuring your company business operation around new computer system are probably over. Nowadays IT budget is pretty limited and corporate management considers IT as regular (not elite) internal services department. So – you, as IT manager or director has limited resources to revolutionize the company, so you follow the step-by-step evolution

o The sunset of proprietary languages. Good example is Great Plains Dexterity – this is the core of recent Microsoft Great Plains, former Great Plains Dynamics. Dexterity had the history of evolution, and now it is using SQL Stored procs to do the majority of database querying and updating, Microsoft plans to phase it slowly out and replace with the future .Net language of choice (not sure which one will win: C# or VB.Net – but this is not important at this moment). In the close future SQL with XML inbound/outbound will be the language of integrations

o The end of heavy custom programming. At least in the US – majority of the project will be outsourced. In the USA we will be mostly dealing with project management and specifications writing, plus physical hardware support. Even if you are dealing with, say Microsoft Business Solutions partner in San Francisco – partner itself will be using either overseas facility or simply contractors over there. When the majority of us will become project managers, thinking about business logic, not the way of realizing it in the code – we will stop heating the opposite platform -no more Microsoft VB.Net programmer hatred toward Java/EJB/J2EE programmer

We are already doing cross platform integrations from Microsoft Business Solutions products: Microsoft CRM, Great Plains to Oracle, DB2, Lotus and other databases, plus Microsoft CRM email messaging through Lotus Domino to begin realize the strategy

Andrew Karasev is Chief Technology Officer in Alba Spectrum Technologies USA nationwide Great Plains, Microsoft CRM customization company, serving clients in Chicago, California, Texas, Florida, New York, Georgia, Arizona, Minnesota, UK, Australia and having locations in multiple states and internationally ( http://www.albaspectrum.com ), he is CMA, Great Plains Certified Master, Dexterity, SQL, C#.Net, Crystal Reports and Microsoft CRM SDK developer.

Author: Andrew Karasev
Article Source: EzineArticles.com
Provided by: Smart cooker

Because of the complexity of Microsoft Exchange Server management and administration, many companies want to consolidate thousands of Exchange users on one server. As a deployment grows, its increasing number of servers can make administrative tasks such as adding, moving, and deleting users extremely time-consuming for Exchange administrators. Administrators must use a combination of applications to administer and manage the Exchange environment, which makes administration of large implementations more difficult. Future versions of Exchange Server will simplify some of these management and administrative tasks and will enable administrators to perform all Exchange administrative tasks through one application. However, for now, Exchange Server’s diversity of tasks and tools leads many companies to want to consolidate as many users as possible on each Exchange Server machine.

Microsoft has been using the Security Development Life cycle (SDL) across its product lines for several years now, and we’ve seen an across-the-board improvement in product security as a result. As a security practitioner, this situation makes me happy indeed, but as an Exchange Server administrator, I want functional improvements to the product as well. Given that Microsoft is already actively working on the next version of Exchange, I wanted to set down a few things I’d like to see in the Exchange Server of the future.

Keep in mind that for every feature we get, there are other features that don’t make the cut. Even with the company’s massive resources behind them, Microsoft’s developers have constraints that prevent them from adding every desired feature while still meeting their schedules and deadlines. That said, here are a few items from my wish list for the next Exchange release.

Let’s start with a relatively easy one: The next version of Exchange should include full support for Outlook Web Access’ premium mode in Firefox and Safari. Multiple-browser support is an important check box for the education market (where you’re likely to find more people using non-Microsoft Internet Explorer browsers), but it’s also something that I would expect to see from the company that pioneered the commercial use of Asynchronous JavaScript and XML (Ajax) in Web applications–not to mention that Microsoft Office Communicator Web Access and all of IBM’s Lotus products already fully support these browsers.

How about certificates? Microsoft Exchange Server has a Certificate Wizard that helps you get the right set of machine names and subject alternative names in your certificate requests. Now that the OCS and Exchange product lines are part of the same business unit within Microsoft, perhaps the two teams could collaborate to produce a single certificate tool that collects all the necessary parameters for certificate requests? Network security and Exchange administrators everywhere would greatly appreciate and benefit from such a feature.

I’ve heard many requests for running Exchange services on Windows Server Core, the bare bones install option with Windows Server 2008; the obstacle here is that the current version of Windows Power Shell won’t run on Server Core. The Windows or Power Shell teams might address this problem on their own; personally, I’d rather they spent their engineering efforts on giving us complete support for running Exchange under Hyper-V.

Nina Swadie is an Online Small Business Support Executive for iYogi who provides detailed information on Online Server Support, in Small Business Server Support, Exchange Server Support, Terminal Server Support, Windows 2000 & 2003 Server, in Server Support, Small business technical support and Windows Server Support etc.

Author: Nina Swadie
Article Source: EzineArticles.com
Provided by: Make PCB Assembly