Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts
Coming soon

Squeaked by on the switch exam with a 790 a few days ago. This was my 3rd time sitting for the exam after a few months studying.

Initially I used the Boson CCNP Network Simulator product materials for prep, but quickly learned that studying the actual Cisco documentation is the best preparation. If I had to do it again I would have bought used switches instead of using the Boson simulator product.

That said, I did use the Boson practice exam as well and I thought the questions were good and helpful with preparing - the material seemed better than the Network Simulator product.

If you've gotten discouraged and have already sat and failed the exam, don't give up.

Good luck and onto route!


Congrats! My 2nd attempt is scheduled this Saturday. Failed the first time with a 776

see more
Original Poster2 points · 2 months ago

Good luck!

I just got boson for TSHOOT. The labs seem to be very basic and low level? Although there are plenty of them. What's your opinion?

see more
Original Poster1 point · 2 months ago

The labs for switch were ok but pretty basic. They did help for the basics but not the advanced stuff.

Load more comments


Hi. Does anyone know if it is possible to migrate packages from MDT to SCCM?

1 point · 1 year ago

No direct path.

But you've got the content in your Deployment Share, and your command lines available.

Unless you have tonnes, it shouldn't be too bad to bring them over manually.

see more
Original Poster1 point · 1 year ago

That is true. Thanks for the reply.

1 point · 1 year ago · edited 1 year ago

I'd have to do some checking at work but I did find a PowerShell script that could migrate SCCM apps to MDT about 6 months ago when I tried using MDT to make my thick image. I can't remember if there was a reverse procedure or not nor do I remember where I found it.

Edit: Looked in my bookmarks and found the link... You may be able to reverse this script to work the opposite way.

A quick Google found this... He's creating packages instead of applications though but it might give you a starting point.

see more
Original Poster1 point · 1 year ago

Thanks for the info. The second link might be something to try.



Any input on this is greatly appreciated!

We are planning on migrating to Ex 2016 from Ex 2010.

Currently we have 2 CAS and 2 MBX servers with no hardware load balancing in place. Total of 5,000 mailboxes.

We'd like to move to a hardware load balancer for the new environment but am unsure at what point and how we might introduce the load balancer as part of the migration.

Should it be implemented before/during/after ?

Thanks for any suggestions/ides.

Original Poster1 point · 1 year ago

Thanks for the input everyone.


I am looking for some feedback on some changes we are going to make in our Exchange 2010 environment.

We currently have 2 mailbox servers (with DAG) and two front end servers using Windows Network Load Balancing.

Current storage is all but used up - we are getting a new SAN shortly.

Once the new SAN in place, we are planning on making all four of our servers to be multi-role (mailbox, client access, hub) and we also will be implementing a hardware based load balancer.

Questions are: - Would it make more sense to create a brand new DAG along with new Exchange 2010 servers instead of attempting to modify our existing environment? - Or, do we keep with the current DAG and create fresh new Exchange 2010 servers which are all multi-role?

We have a fairly large environment (2000 mailboxes) - the most important things for the deployment are stability and uptime ...

Thanks for any help!



If you have the resources available, I would deploy four new servers and add them to the DAG. Allow databases to replicate, remove the copies of the old servers and remove the old servers from the DAG.

If you're not going to change the namespaces, there's not much to switch to a proper load balancer than to change the DNS record to point to the VIP or even swap the existing shared IP and move it to the new load balancer.

see more
Original Poster1 point · 2 years ago

Great, thanks for the info.

I like the idea of creating new servers possible new dag and migrating over to that vs modifying existing installs

No need to create a new DAG, just add the new servers to the existing DAG and remove the old ones afterwards.

By the way, four servers for just 2000 mailboxes? If this is not a site resilient deployment or if there aren't specific availability requirements, that seems like an overkill.

see more
Original Poster1 point · 2 years ago

Well, the OS will be different on the new servers 2012 vs 2008 so I think we will need a separate DAG, as the OS has to match from what I understand. Agreed it is a bit overkill, but HA is the goal.

Load more comments

Cake day
August 10, 2016
Trophy Case (2)
Two-Year Club

Verified Email

Cookies help us deliver our Services. By using our Services or clicking I agree, you agree to our use of cookies. Learn More.