Beruflich Dokumente
Kultur Dokumente
UsefulNot useful
SearchSearch
Upload
ENChange Language
Home
Saved
Bestsellers
Books
Audiobooks
Magazines
Documents
Sheet Music
Download
Jump to Page
3.6K views
2Up votes, mark as useful
0Down votes, mark as not useful
Exchange 2010 Interview Question answers
single set of Transaction log files. Storage Groups are managed using their separate server
process and theidea behind splitting databases up in Storage Groups is primarily to reduce the
overhead that results from multiplesets of
(although raised to 75 GB when Exchange 2003 Service Pack 2 was applied). There was no
limit on adatabase size
when talking about Exchange Server 2003 Enterprise edition {well actually there is a
16Terabyte limitbut this limit is
caused by hardware).Exchange Server 2007 comes in two flavours, a standard edition and an
enterprise edition, just like previousversions
of Exchange. The Mailbox Server when talking about the Exchange Server 2007 Standard
edition supportsa total of 5
Storage Groups and 5 databases. Unlike Exchange 2003 and previous versions of Exchange
there's no longer a
database storage limit in the standard edition. The Mailbox server in the Exchange 2007
Enterprise edition supports
up to 50 Storage groups and a maximum of 50 databases per server. Exchange 2007 allows
you to create up to 5
databases in each Storage Group as is the case with Exchange 2003, but best practice is to
create 1database per
Storage Group. So why should you have a one to one relationship between storage groups
and databases? Well
primarily because you'll be up and running a lot faster considering disaster recovery
scenarios,etc.No Storage Groups In Exchange 2010.•• Exchange 2010 has only mailbox
databases and they are organizational objects in EMC. Mailbox databases no longer
connected to the server object they become *Peers•. Database management has also been
moved from Server configuration node in exchange console EMC. The mailbox databases
are placed in the Organization Configuration ->Mailbox location in the console rather than
the server level in
exchange 2007. The database names has to be unique through out the exchange organization
as well. This means
that we can't have duplicate mailbox database names like in 2007 (in different storage groups,
of
course). As there are no storage groups, this will also mean that the database will have its ow
n logs aswell...One of the goals of ESE in Exchange 2010 is to reduce the cost of maintaining
and managing a database. Database maintenance is comprised of several tasks that manage
and keep the integrity of your mailbox database.
Database maintenance Is divided Into thefollowing:
Store mailbox maintenance
to increase performance. In Exchange 2010, on large or very heavy profile servers, the store
mailboxmaintenance
task only lasts approximately 45 minutes, while ESE database maintenance usually took from
six toeight hours per
night to complete on large Exchange 2007 databases (2 GB quotas). In
Exchange 2010, improvements have beenmade to support both large mailboxes as well as to
support JBOD storage and storage without the use of RAID.
Microsoft Exchange Server 2010 includes many improvements to the
Exchange databasearchitecture:
•
Public folder reporting has been enhanced.
•
Databases are no longer associated with storage groups. Storage groups have been removed.
•
Investments in store schema and Extensible Storage Engine
{ESE) optimizations have reduced lOPS by 70percent.
Describe the differences in the permission model between Exchange 2003 andExchange
2010.
Exchange 2003 Security and PermissionsModelTo help simplify management of
permissions, Exchange Server 2003 provided predefined security roles that wereavailable in
the Exchange 2003 Administrative Delegation Wizard. These roles were a collection of
standardizedpermissions that could be applied at either the organization or
the administrative group level.In Exchange 2003, the following security roles
were available through the Delegation Wizard in Exchange SystemManager:
Exchange Full Administrator Exchange Administrator
Exchange View Only Administrator
Thismodelhadthefollowinglimitations:
A lack of specificity. The Exchange Administrator group was too large, and some
customers wanted to manage their security and permissions model at the individual server-
level. A perception that the Exchange Server 2003 security roles only differed in subtleways.Th
ere was no clear separation between administration of users and groups by the
Windows (Active Directory)administrators and Exchange recipient
administrators. For example, to perform Exchange recipient related tasks, youhad to
grant Exchange administrators high level permissions (Account Operator permissions
on Windows domains).Exchange 2007 Security and PermissionsModelTo improve the
management of your Exchange administrator roles, which were called "security groups" in
Exchange2003, the following new or improved features have been made to the
Exchange security and permissions model:
•
Deprecated storage groups
•
Mailbox databases no longer connected to the server object
•
Improvements in Extensible Storage Engine (ESE) for high availability, performance, and
database mobility
•
Flattened Outlook store schema
•
Enhanced reporting with public foldersIn
Exchange 2010, the store schema has been changed to
remove the dependency of mailbox databases onthe
server object. In addition, the new schema has been improved to help reduce database
1/0
persecond(lOPS) by refactoring the tables used to store information. Refactoring the
tables allows higher logical contiguityand locality of
reference. These changes reduce the store's reliance on the secondary indexes maintained by
ESE. As a result, thestore is no longer sensitive to performance issues related to the
secondary indexes.Store resilience and health has also been improved by adding
several features related to detecting and correctingerrors and providing alerts, such as the following:
•
Mailbox quarantine on rogue mailboxes
•Transport cut-off to databases with less than 1GB of space
•
Thread time-out detection and reporting
Name the system prerequisites for installing Exchange 2007 in your existing ActiveDirectory forest.
Windows Server 2003/R2 x64 SP2Windows Server 2008 x64
Microsoft .NET Framework Version 3.0/Microsoft .NET Framework Version 2.0 (with
update/SP1)Microsoft Windows PowerShellMicrosoft Management Console (MMC)3.0Network News
Transfer Protocol (NNTP) service must not be installed.Simple Mail Transfer Protocol
(SMTP) service must not be installed.liS {forOWA)
Name the system prerequisites for installing Exchange 2010?
1-
GeneralPrerequisites:
Make sure that the functional level of your forest is at least Windows
Server 2003, and that the Schema Master isrunning Windows Server 2003 with Service
Pack 2 or later.
The full installation option of Windows Server 2008 SP2-64bit or Windows Server 2008 R2-
64bit must be used for allservers running Exchange 2010 server roles.Both Windows Server 2008
SP2-64bit or Windows Server 2008 R2-64bit Standard
&
Enterprise are supported and wecan use them to install
Exchange 2010.DNS must configure correctly in your Active Directory forest. All
servers that run Exchange Server 2010 must beable to locate Active Directory domain
controllers, global catalog servers, and other Exchange servers.For all server roles other than
the Edge Transport server role, you must first join the computer to the appropriateinternal
Active Directory forest and domain.
2-
Operating System Components Prerequisites:
Web-Metabase
Web-L.gcy-Mgmt-Console
Web-Basic-Auth
Web-Digest-AuthWeb-Windows-Auth
Web-Dyn-Compression
Net-HTIP- Activation
RPC-over-HTIP-Proxy3-
Software Prerequisites:For Hub Transport or Mailbox server role, Microsoft Filter Pack is
required to be installed. You can download theMicrosoft Filter Pack from the Microsoft website.
How would you easily install all the Windows Server 2008 R2 roles and featuresrequired
for Exchange 2010?
Exchange Server 2010 Service Pack 1allows us to
install all Operating System prerequisites using just theExchange
Setup wizard. When we use the Exchange Server 2010 SP1 Setup wizard, there is a new
option called Automatically install Windows Server roles and features required for
Exchange Server. Just by clicking on thatoption will be
copy an update rollup to the Updates folder. In this scenario, the update rollup package is
applied duringthe
installation of Exchange. The Updates folder supports only new installation of Exchange
server.
Name a few reasons for using 64-bit hardware and OS version for Exchange 2007-2010.
64-bit hardware provides the system architecture that is required to support the increased
memory, storage, andenhanced security requirements in a more cost-effective manner. Trends
indicate that demands on messagingsystems will continue to grow and 64-bit servers provide
the system architecture to meet these demands whilereducing costs within organizations
through server and disk storage consolidations. With a larger addressablespace,
the Exchange servers can utilize more memory thereby reducing the required input/output per
user (lOPS),enabling the use of larger disks as well as low cost storage such as SATA2
drives.
Exchange2007 came in both 32-bitand 64-bit versions. Name a couple of
reasons for ever needing the 32-bit version.
You need exchange 2007 32bit to export mail box into PSTfile.
Wanting to manage Exchange 2007
-
2010 from a remote computer, name a few of your
managementoptions.
There are a few options for managing Exchange 2007 servers remotely. First
off,
you can install the Exchange 2007management tools onto a separate machine from
your Exchange server, as long as that machine is running either
the 32-bit or 64-bit version of Windows Server 2003 Service Pack 1(SP1) or later, Windows
Server 2003 R2, or Windows XP SP2 or later. Note that installing any of the server roles
(client access, mailbox, edge, and so on) on32-
bit hardware is not supported in production environments, but is supported for installing the
management toolson a
are visible so you can perform operations on any of them remotely. In the shell, many of the
tasks supporta filtering
flag like -server if you want to scope an operation to a single server. There are a few
exceptions,however, for
Bacqround Jobs
:
Also called a PSJob,
it
allows a command sequence (script) or pipeline to be invokedasynchronously. Jobs can be
run on the local machine or on multiple remote machines. A PSJob cannotinclude
decoupled from the scripts and allow localized string resources to be imported into the
script at runtime(Script
line & columns, commands and read or write access of variables. It includes a set of
cmdlets tocontrol the
breakpoints via script.Eventing: This feature allows listening, forwarding, and acting on
management and system events. Eventing allowsPowerShell hosts to be notified about state
changes to their managed entities. It also enables PowerShell scripts tosubscribe to
ObjectEvents, PSEvents, and WmiEvents and process them synchronously and
asynchronously.Windows PowerShelllntegrated Scripting Environment (ISE)
:
PowerShell 2.0 includes a GUI-based PowerShellhost
which only allow a configured subset of PowerShell to be invoked. The new APis also
supportparticipation in a
when?
Setup.com is used for all preparation work; basically it calls different backend procedures.
Setup.com is also usedin
server and place each role, or a combination of roles, on different servers in the
organization. With currentExchange
servers you can make a server a Front-End server, or a Back-End server and that is about
it.Exchange 2007
introduces five roles to the Exchange organization.Edge Transport- The last hop of outgoing
mail and first hop of incoming mail, acting as a "smart host" and usuallydeployed in a
perimeter network, Edge Transport provides mail quarantine and SMTP service to enhance
security.One advantage of this role is that is does not require Active Directory access, so
it
can function with limited accessto
the corporate network for increased security.Hub Transport- The Hub Transport role handles
mails by routing them to next hop: another Hub Transport server,Edge server or mailbox
server. Unlike Exchange 2003 Bridgehead that needs Exchange admin defined routinggroups,
Exchange 2007 Hub Transport role uses AD site info to determine the mail flow. The Hub
Transportand Edge
Transport servers are very similar and in fact, one can forgo the Edge Transport server
andconfigure the Hub Transport to accept mail from, and send mail to, the Internet.Client
Access -The Client Access server role provides the other mailbox server protocol access apart
from MAPI.Similar to Exchange 2003 FrontEnd server,
it
enables user to use an Internet browser (OWA), 3rd party mail client(POP3/IMAP4) and
mobile device (ActiveSync) to access their mailbox.Mailbox- The Mailbox server role is
responsible for hosting mailbox and public folder data. This role also providesMAPI access
for Outlook clients. Note that there is also a variation of this role called Clustered Mailbox
role, for usewith high-availability MSCS clustering of mailbox data. When Clustered
Mailbox role is selected, other server rolescannot be combined on the same physical
server.Unified Messaging- This role enables end users to access their mailbox, address book,
and calendar usingtelephone
and voice. IP-PBX or VoiP gateway needs to be installed and configured to facilitate much of
thefunctionality of this
server role.
What are the benefits of using roles, vs. the way Exchange 2000/2003 worked?
Server role is a logical concept used to organize Exchange2007 services and features across
one or more servers.While Exchange2003 provided primitive server roles called
BackEnd server and FrontEnd server,Exchange2007 hasmore granular
divisions.Dividing Exchangefeatures among several server roles has advantages:
More flexible deployment topology: For a small or medium company that has only hundreds
of mailboxes and allusers are centralized, customer can install all required roles on one
physical server. For a large enterprise wheretens of thousands of mailboxes span multiple
physical locations, customer can choose to deploy each role on aseparate
server or even multiple servers per role to provide better performance and fault
tolerance.Better hardware utilization and scalability: Because each role only installs binaries
and runs services for a specificfeature set. Unlike older versions of Exchange, configuring a
server that has only one or two roles will reduceMemory, CPU and disk space requirements
for this server. In addition, roles are scalable so admin can loadbalance
work of one role to multiple servers.Easy to maintain: Upgrading, applying hotfix, or other
server changes that could cause server outage can beisolated to one server role. This reduces
maintenance down time and end user impact. Admin can also install or uninstall roles on a
server as needed.
What are the Exchange 2003 equivalents of the various Exchange 2007-2010roles?
unlike the previous versions, Active Directory does not need to be prepped beforehand, it is
doneautomatically
during setup, but the option does exist to allow for manual schema upgrades. During the
setupprocess the server
will connect to the Schema Master in an effort to update the schema and this requires thatthe
Schema Master is
available and that the account you are running setup with has permissions to modify theschema.
If you wish to prep the domain manually, you can do so with the /PrepareAD switch on any
server in the samedomain that the Schema Master is in but
it
is recommended to do this on the Schema Master. Once you havecompleted this, you will
have to wait for the schema updates to replicate throughout the forest before you installany
additional Exchange
2007
servers in the organization.Preparing Active Directory manually offers more options than
before and there maybe more commands for you to
configures the other domain, or domains, in the forest. It does not need to be run on the
domainthat you run
/PrepareAD in, but any additional domains will need this command run. You have three
command line options withthis command.
Setup.com /PrepareDomain- Prepares the
current domainSetup.com /PrepareDomain:FQDN of target domain to beprepped
Exchange2007.
•To run the Setup /PrepareSchema command, you must be a member of
the Schema Admins and Enterprise Admins security groups.•To run the Setup
/PrepareAD command, you must be a member of the Enterprise Admins security
group.To run the Setup /PrepareDomaln, setup /PrepareDomaln:<FQDN> command or the
Setup /PrepareAIIDomalnscommand, you must be a member of the Enterprise Admins group
or you must be a member of the Domain Adminsgroup in any domain that you will prepare.
You have an Exchange 5.5 organization and finally decided to move forward and upgradeto Exchange
2007/2010. What's your next obvious step?
Install an intermediary Exchange 2003 server. Then move mailboxes from Exchange 5.5 to
Exchange 2003 usingExchange 2003's toolset, and then move from Exchange 2003 to
Exchange 2010 using its toolset.
You're looking to install Exchange 2007-2010 and Outlook on the same machine.Should
Created
by
Aslam Kader
machine to export mailbox data to a .pst file.
How would you verify that the schema was in factupdated?
You can
verify
that you
are ready
to start lnstalll111 &change
2JX11
by
looklnB
for
tile followlnr.
1. The Microsoft bchan&e
Systems
ObJects container conbllns
a
efobaleroup called &chanp 12Domain
Servers
2.
The ESUG
has
the
Ewdlanp
12
Domain
Servers
slobal group as a member.
•
The ESUGwill have permissions
to
the ManqeAudltln&and Security
Loc
setlfi'IIS
on all
DCs
In all domainst l l a t t h e e o m m a n d s
were
nan aplnst.
How WO\IId you check your Exchange c:onfiiuration settings
to
see
if
they're
right?
What types
of
permissions
are conffaurable for bchan. e?
•
Exchangefull admln- full control over tile exchange orpnlzatlonIncluding permission
2)
ExchanseAdmin-Manageeverythingwltlllntile
orsanlzatlonexcept011permission.3 ) E x c h a n s e
view
only admlnlstratnr-
read
only administrative
access
to ExchanseO " B a n l z . a U o n
How
can you pant access
for
an administrator
to
access
all
mailboxes
on a
specific:
server?
Grant
permlulonl on
a llll.lda
11'8Rba
Use
the
followlllf command
to
srant
aaleSS
to
Just one mailbox:
A d d · M a l l b o x P e r r n l s s l o n · I d e n t i t y• •
-user
<UserorGroupldenllty>
-Aa:essRJ&hts
F U I I a a : e s s - l n h e r l t a n c e T Y p e all
Note:the User parametercan in
faet be
either users or groups, the parametername
user"
is a
bit
misleadinsl
A d d · M a l l b o x P e r r n l l s & l o n ·Identity"Test"
-User
Administrator
·AccessRights
F U I I a c o e s s - l n h e r t t a n c e T Y p e all
Or If
I
want
to add tile
security
Group Group2:
A d d - M a l l b o x P e r m l l s & l o n ·Identity"Test"
-User
Group2·AccessRI&htsFullaccess-lnherttanc:aTYpe
all
Related Interests
Prakash Kumar
Exchange-2010-Interview-Question-and-Answers-41-Pages.pdf
UPLOADED BY
kunwar_sd
Tsuchinoko123
hkush78
Neetu Jain
Ulaga Nathan
manjutgx
Subodh Jumle
Storage Group
UPLOADED BY
anilpshinde2605
Exchange questions
UPLOADED BY
amithdsouza
kunwar_sd
amlesh80
Exchange 1
UPLOADED BY
pks1011
Rajasekar Parthasarathy
2010.doc
UPLOADED BY
kunwar_sd
Argho Das
Sravanthi Reddy
vishwah22
bnhamz
Oudaye Ramdhean
What is Exchange Server
UPLOADED BY
kmrs_888
DAG MSExchange
UPLOADED BY
Mohamed Ali
Surendra Yadav
manishjain79
2010.doc
UPLOADED BY
kunwar_sd
kunwar_sd
RAID 5&Mirroring
UPLOADED BY
kunwar_sd
kunwar_sd
2010.doc
UPLOADED BY
kunwar_sd
kunwar_sd
kunwar_sd
kunwar_sd
129884223-exchange-interview-questions-with-answers.pdf
UPLOADED BY
kunwar_sd
kunwar_sd
Exchange 2013
UPLOADED BY
kunwar_sd
2010.doc
UPLOADED BY
kunwar_sd
BES 5
UPLOADED BY
kunwar_sd
kunwar_sd
kunwar_sd
BES
UPLOADED BY
kunwar_sd
kunwar_sd
002. eBook Correct Your English Learn to Speak More Like a Native
UPLOADED BY
kunwar_sd
Visual_CertExam_Suite_3.2.1.rar -VirSCAN.org.pdf
UPLOADED BY
kunwar_sd
kunwar_sd
PTEA-Teacher-Notes.pdf
UPLOADED BY
kunwar_sd
advise_238723_20150521.pdf
UPLOADED BY
kunwar_sd
New_Online_Appointment_Booking_Process.pdf
UPLOADED BY
kunwar_sd
kunwar_sd
313763909-Exchange-2016.pdf
UPLOADED BY
kunwar_sd
263833757-The-Official-Guide-PTEA-Teacher-Notes-v1-OG.pdf
UPLOADED BY
kunwar_sd
kunwar_sd
Footer Menu
Back To Top
ABOUT
About Scribd
Press
Our blog
Join our team!
Contact Us
Invite Friends
Gifts
SUPPORT
Help / FAQ
Accessibility
Purchase help
AdChoices
Publishers
LEGAL
Terms
Privacy
Copyright
Social Media
o
o
o
o
o
EnglishChange Language