New Horizons, PLA, along with a variety of technical partners, is once again celebrating the quickly changing landscape of Information Technology. Techknowledgey 2013 will introduce you to the tools, products, and strategies that Modern IT departments use today and will introduce over the months ahead. Multiple sessions discussing collaboration tools, cloud technologies, system integration, and the latest operating systems, will get you the information you need today to make proper business decisions tomorrow.
Date: Thursday, December 12
Time: 8:00AM - 5:00PM
Location, New Horizons, 14115 Farmington Rd., Livonia, MI
Comments(0) Add a Comment
Microsoft System Center 2012 Configuration Manager includes built-in migration tools, and one of the key features of the migration tools is the ability to use Shared Distribution Points. This allows for a smoother transition between environments by allowing the new ConfigMgr 2012 site to use existing Distribution Points in the old site (ConfigMgr 2012 or SCCM 2007) as content locations while clients in the old site continue to function normally. Moreover, once the clients that use an SCCM 2007 DP are upgraded, the DP can be upgraded to a full ConfigMgr 2012 DP and all of the content in the CM07 distribution share is copied into the CM12 content libary, alleviating the need to redistributed massive amounts of content across the network. All that is required to enable this great feature is a simple check box when the Source Hierarchy is identified:
With that as a major component of most migration strategies, configuring a Source Hierarchy for migration only to discover that none of the Distribution Points show up can be a show stopper. Consider this example where an SCCM 2007 site was configured:
There is only one server that appears after the data gather, and it’s the Primary Site Server (the Primary has the Distribution Point role assigned, but note that it is not eligible to be upgraded). When we look in the CM07 console though, we see there is another server in the site: a Distribution Point that we would really like to leverage between both environments.
So why aren’t we seeing our Distribution Point as an option for a Shared DP?
Buried in the TechNet migration prerequisites documentation is a single line in the “Shared distribution points” section that makes all the difference:
For each source site, only the distribution points that are installed on site system servers that are configured with a FQDN are shared.
So let’s add the FQDN of the server to the properties…
…and tell ConfigMgr 2012 to Gather Data Now.
Now when we refresh, we see that our DP shows up under Shared Distribution Points and is available for upgrading:
While it is generally not common practice to omit the FQDN from site server roles in SCCM 2007, there are some environments where this is done for various reasons so it’s important to plan for adding this configuration setting prior to migration activities if Shared Distribution Points are a major part of the migration strategy.
- Phil Schwan, Technical Specialist.
You can read more posts by Phil at My IT Forum.
Comments(0) Add a Comment
As I discuss IT strategies and roadmaps with companies, the term BYOD (bring-your-own-device) comes up nearly 100% of the time. Time and time again, I would hear “we are currently talking to MDM (mobile device management) vendors and getting demos so we can implement a BYOD strategy.” A software solution should not drive the ‘strategy’ and prior to going through a software selection exercise a true strategy should be defined. Let me explain. In reality, the “strategy” is not in a software product or devices but begins at the business level and then the technology should be chosen to enforce/drive the strategy.
As you read this, you may wonder what does he mean? What I mean is when defining a BYOD strategy, it should begin on paper in the form of governance and policies that would be shared with the BYOD user community. Some examples of the governance and policies that should be defined would include:
- What does the business intend to achieve by implementing BYOD? Cost savings (if so, in what areas – devices, support, head count, etc.)?
- What kind of device assortment are being used today or what devices would they buy? Was there a user facing survey done?
- Does the firm want to limit the devices that the BYOD program would cover?
- What would the reimbursement policy be and how will the users submit for it?
- How does an employee enroll in the BYOD program?
- What rights does the company have to the device once they connect to the corporate network? What can or will be wiped if the employee loses the device or leaves the company?
- If there is a support issue with the device hardware who will support it? For example, if their iPad screen goes out do they bring it to IT or go to the Apple store themselves?
After these policies are defined, documented and approved by the company brass is when the technology comes into play. All the leg work would be done to develop a questionnaire or requirements to share with potential MDM and SaaS vendors to see where their solutions may or may not fit before going to the next step of demo, PoC, and pilot. Without this upfront planning and due diligence, there would be a very high risk of the BYOD program failing due to lack of user adoption, increased IT support overload, and unrealistic expectations which would lead to bad press internally.
- Neil Parekh, Practice Director
Comments(0) Add a Comment
Strategies to help design, implement and manage disaster recovery and business continuity framework to protect your organization’s core IT assets, people, and processes.
*PLA will be exhibiting with Silver Peak and Tegile Systems
The current economy can present all sorts of challenges that IT has to work through including less staff, financial resources and money to spend. At the same time, companies have to make sure that in order to survive, their systems which support IT, are resilient and highly available.
Your system crashing is inevitable! Never mind the reason. The goal is to make sure you have an infrastructure that is as resilient as possible so that it can meet business needs in the event of a disaster. There are steps you can take to maximize your availability and prevent significant downtime.
The content of this one day conference will help you in determining the right level of availability protection, how to design, implement, test and get management buy-in for a highly reliable network infrastructure.
Date: September 12, 2013
Location: Donald E. Stephens Convention Center Rosemont (O’Hare) Illinois
Comments(0) Add a Comment
By now everyone should know that Microsoft released Windows 8.1. Today at the Build conference Steve Ballmer, Microsoft’s CEO, explained (in that awesome loud tone he has) the new strategy moving forward will be faster releases of products in iterations — engineering is moving faster than marketing and this could be a good or a bad thing depending on the organization. This change is similar to Apple OS release methodology where you can purchase an iteration of the OS at a minimal cost. I personally couldn’t be more thrilled with the change because it effects all the products Microsoft sells.
I’m a fan boy of Microsoft so of course I’m happy with this change but I’m also an architect who needs to make sure the solutions I design and recommend meet the requirements of customers. You’d be surprised at the number of customers still on Windows XP and SharePoint Portal 2003 – if you’re a consultant like me maybe you’re not that surprised.
A few days ago I was explaining some of the changes in Windows 8.1 to my other half who said “so basically it’s Windows 7 again”. I think I just said “umm something like that” but the truth is it isn’t. 8.1 was designed based off feedback from customers much like the Xbox One. Microsoft is hearing what customers are saying and improving the products based on that feedback in a lightning speed fashion — This is HUGE people. It’s our jobs as consultants to help companies (from small business to Fortune 500) get to the next generation of products. With 8.1 you can now boot to your desktop, use the traditional Windows 8 touch or have a better experience with a mouse. Get more information and download your copy here.
I love the idea of the Microsoft App & SharePoint Store because I can do stuff like this to my desktop…. Isn’t my nephew adorable in my Windows 8 tiles.
My Windows Surface RT 8.1 Upgrade
First I’d like to point out I have an iPad (latest gen) and iPhone 5, this will matter later on. I bought my Surface RT from a friend last year after Build, yes one everyone got one for free at Build (Thanks Anthony). I started using it for OneNote and Word and the SkyDrive integration. It came with the Touch Keyboard and I just couldn’t get used to it so I bought the Type cover. Since then I’ve noticed the App eco system has grown, yes even for RT, and I’m using my Microsoft Surface RT more than my iPad. I use it for work and personal stuff. I heart the “Windows Everywhere” experience in Windows 8 because my desktop Windows 8 Enterprise follows me without issues on my Windows devices. The one thing I didn’t like about the RT was it was missing Outlook and I don’t know how to function without Outlook. Well it’s over and I’m so excited to have 8.1 Installed on my Surface.
Here’s all I did and my upgrade process was flawless.
1. I made a Recovery disk on a USB drive, as recommended, here are the instructions.
2. Open the App Store and choose to download Windows RT 8.1 Preview. Note: That took about 2 hours to download.
3. After it was done I choose upgrade, then agreed to the terms, it migrated all my content, had me verify my account via text message and there you have it.
Here are some images of my Surface RT running on Windows 8.1
Start Button, This PC, Outlook… On the start screen you can press any App to make groups.
Outlook running on my Surface!
- Kris Wagner, SharePoint MVP
You can read more posts by Kris at SharePoint Kris.
Comments(0) Add a Comment