Yes, it's true. The Microsoft Services Managed IP solutions group has been working for the last few months to package up ZTP 3.0 with current fixes and updated documentation to release as ZTP 3.1. Ironically, this is about the same place we were with this same team over a year ago, but they have a few new people and seem more motivated. This same team is also developing ZTP 4.0 based entirely on ILM 2.0 (and they may be searching for another build-with customer). I expect that ZTP 3.1 will be a formal Microsoft Services Core IO Service Line Offering in Feb or March and that ZTP 4.0 won't be generally available until late 2008 (though build-with customers may see multiple releases this year). May you be provisioned a happy new year.

A common question around Zero Touch Provisioning has been, why use BizTalk Server and Human Workflow Services? 

Answer: We started ZTP in 2003, when BizTalk Server 2004 was in pre-beta and HWS was one of the premier features of the release. We made a big bet that workflow would change the way distributed applications could be designed. As it turns out, it was the right bet, but the technology from HWS was very complex and had problems with shipping some features. Once it was determined that HWS was not going to be the premier workflow platform (around BTS 2004 RC), we already had too much invested in HWS to back it out. Fast forward to April 2006, there still wasn't another workflow platform from Microsoft publicly available. So, we continued with BizTalk Server 2006 to release ZTP 3.0 by the end of summer 2006. We released ZTP 3.0 in October 2006 and .NET Framework 3.0 released in November 2006 with Windows Workflow Foundation.

Now, we're planning Provisioning 4.0 to leverage Windows Workflow Foundation. BizTalk Server will still be used for what it is best at: integration scenarios. Talking with enterprise applications (like SAP, PeopleSoft, JDE, etc) and external partners (like procurement, supply chain, etc). Also, BizTalk Server has excellent features around business monitoring (BAM). Savvy customers will want to use Provisioning 4.0 with BizTalk Server 2006 to enable near real-time request and workflow monitoring against key performance indicators (KPIs). Ironically, BizTalk provides a lot of core services that is not included with the WF framework (like a host process, pub-sub messaging, correlation, routing, health tracking) that will need to be built or leverage another WF host model (like SCSM and ILMv2). Therefore, BizTalk Server will not be required by Provisioning 4.0, but may still be leveraged.

At TechEd and via email, I've had many questions about the future of Zero Touch Provisioning. Here's some information in an FAQ form:

1. Is it true that ZTP v3.0 is the last version? Why is Microsoft passing over this solution?

Answer: v3.0 is likely the last version to be called Zero Touch Provisioning. However, there's a Microsoft Services solution group project code named Provisioning 4.0 that is based on the ZTP 4.0 planned architecture. To be clear, Microsoft isn't missing out on this opportunity, rather we’re investing more into the solution development and marketing. Just remember, more investment means more project rigor and financial measurement, which can lead to delays or scope changes.

2. What is the future Provisioning strategy with future Microsoft products like System Center Service Manager and Identity Lifecycle Manager v2.0?

Answer: Provisioning 4.0 will continue to be a common request and workflow engine across the Windows Server System and across IT disciplines. As Microsoft's products evolve and adopt WF technology, Provisioning 4.0 should support even more cross product integration actions and new product hosting. The goal of Provisioning is to enable self-service and task delegation for any activity across the platform (software, service, or device). On the technology side, we're moving to Windows Workflow (just like our products) to match the common technical architecture direction for all workflow at Microsoft and plan to provide WF activities for our products.

3. OK, but I saw a demo of Self-Service Provisioning on Service Manager using Configuration Manager to deploy an application.

Answer: Yes, this doesn't preclude products from shipping SDK samples, adapters, or solutions for specific high-value scenarios. However, Provisioning 4.0 spans Deployment Management, Configuration Management, Identity Management, Operations Management, and Service Management. Ideally, Powershell automation and Provisioning Packs will become common engineering criteria like Management Packs.

A main tenet of Provisioning is to protect the solution investment while enabling our future products. This may mean that some functionality delivered today in custom code will be moved into product features, but the overall investment in the solution is preserved by expanding service definitions and integration scenarios. In other words, if you are solely concerned with provisioning for 1 IT discipline, then an eminent product may be a better choice, but each provisioning scenario decreases investment risk dramatically and pushes you toward Provisioning 4.0. In fact, Provisioning 4.0 could enable transitioning to future Microsoft products faster.

4. So, who owns Provisioning at Microsoft?

Answer: Today, Provisioning is a Microsoft Services solution, now owned by the formal solutions group. However, it is not farfetched to picture certain Provisioning Packs as SDK samples, adapters, or solution accelerators licensed for specific products. In the long run, I hope to see Provisioning as a common product feature with a shared architecture across the Windows Server System.

5. What does this mean for David?

Answer: I’m not sure, but I may not be working on Provisioning for much longer. The solutions group has Architects, Program Managers, Development Managers, Product Managers, and teams of developer/test resources. Ironically, it’s not clear that there is room for me. I’ve been working on Provisioning since 2003, both with world class resources like Brandon (Danny and Graham, or Nilesh, Balaji, and Dave) and sometimes by myself. It’s very satisfying and scary to see my vision take hold and live beyond my control. Perhaps it’s time to let Provisioning fly without me. Then again, it would be awesome to work with the various business groups to more formally productize Provisioning.

After feverishly rebuilding my demo (literally up to the last minute) and trimming slides (based on feedback), I finished my presentation in 50 minutes (of 90). Ahh! I guess I should have kept a few more slides. Also, I had to change the demo’s I showed to simpler scenarios because I couldn’t complete the rebuild with the MIIS services. And, common feedback was that I talked way too fast. This is the first year I used the speaker training and the worst evaluation scores I’ve ever received. On the plus side, I was able to have an extended Q&A session with some of the attendees.

Zero Touch Provisioning v2.0 is used by multiple partners at many customers in Sweden. Unfortunately, there's been confusion with contracts and some problems with engaging Microsoft Services to provide partners with access and redistribution rights to v2.5 and now v3.0. Microsoft is a big company with lots of legal entities and opinions. I've been on leave for quite a while now, but before I left we began working on the partner release strategy for v3.0. I return to work next week and I'm excited to say that there's some good news for partners. We should be close to finalizing the v3.0 partner strategy, including source access and services for partners (like training and support). ZTP v3.0 will continue to be a Microsoft Services offering, available to partners and customers, but the contracts and costs will be commonly set and more easily obtained.

To partners in Sweden (like Spintop and WMdata), sorry for taking so long and I hope you haven't given up on us. Thank you for using Zero Touch Provisioning. The ZTP v3.0 framework and toolset is very powerful. I truly expect 2007 to be the year of Provisioning and even hope to visit customers and partners around the world to train on v3.0 and discuss v4.0.

I haven't blogged in a while because I'm too distracted to go to my blog and endure the process of posting. However, I installed Office 2007 Beta 2 Tech Refresh today and Word 2007 has a "publish to blog" feature. It's fairly simple to use and I hope it will encourage me to blog more.

Lately, I've been asked from multiple customers and partners about the future of Zero Touch Provisioning. ZTP is still alive and growing.

As a reminder, ZTP has been an MS Services solution from the beginning (starting in 2003), but version 2.0 became public access (with documentation) thru the BDD team. The original concept, spec, and code base was built (thru engagement) for 1 large customer/partner, then expanded to better support more customers, version 2.0 shipped with BDD 2.0 on TechNet (November 2004), and finally, I've made multiple updates to 2.0 available on GotDotNet (last one from March 2006).

The current version available from Microsoft Services is ZTP v2.5. It is still based on BizTalk Server 2004. This version is only available and supported as a Microsoft Services engagement with a work order that protects Microsoft ownership and redistribution rights. For a partner, this requires an MCS work order of type P4.

v3.0 is in development (beta in July, release in August) and supports BizTalk Server 2006 (and much more). Currently, this version will only be available and supported as a Microsoft Services engagement with a work order that protects Microsoft ownership and redistribution rights.

v4.0 will support .Net Framework 3.0 (including Windows Workflow Foundation), Windows SharePoint Services v3, and integration with System Center Service Desk. It is planned for H1 2007.

Well, after many months, ZTP 2.5 is generally available through an MS Services engagement. We'll maintain source (features and bug fixes) through a Services engagement model (requiring Consulting Services for initial deployment or Premier Services for maintenance).

Q: What’s new in ZTP 2.5?
• Active Directory ServiceAdapter for WS queries to AD
• Combined status across ZTP+HWS
• Web Services for all ServiceAdapters and Administration
• New Web Parts: Navigation multi-view, Common Services, Pending Requests, Service Description, Administration tool
• Updated UI to match SharePoint styles and templates
• Updated User Controls modified to use Web Services and SharePoint styles/templates
• Sample Call Service Orchestration to batch updates to ZTP
• Sample Bulk Update Manager User Control for querying Active Directory
• Bug fixes increasing scalability and performance

There are some interesting features in VSTS for use in Agile Development, but the new VSTS view of architecture is a little confusing. I'm not confident the leading and trailing shadow concept will shed light on the benefit (pun intended). Read more at http://msdn.microsoft.com/vstudio/teamsystem/msf/msfagile/.

Though a goofy name, Windows Workflow Foundation (WF) is a powerful development framework to enable in-application worfklows. From base approval process to means of leveraging useful design patterns without building your own infrastructure from sratch. If you want to write code in .NET 2.0, I highly encourage you check out WF. You can learn more at http://www.windowsworkflow.net/Default.aspx.

edited TLA to WF

then you should definitely check this out:

FIX: Generation 1 garbage collections and generation 2 garbage collections occur much more frequently on computers that have 4 GB or more of physical memory in the .NET Framework 1.1

http://support.microsoft.com/?id=893360

In early 2003, Tony, a Director in Microsoft Services who branded Zero Touch, asked Brandon and I to review a prototype tool in development called DEAPS and determine if it was viable as a self-service provisioning application for an outsourcer. It was built on ASP.NET web interface posting to BizTalk Server 2002 orchestrations. Each workflow was an independent orchestration and required someone to know BizTalk to change operations. The UI was nice with a custom delegation model, but the engine didn't take advantage of our new (then, soon to ship) platform technologies, like WSS, Authorization Manager, BizTalk Rules Engine, and Human Workflow Services. Ultimately, we decided that it didn't meet the needs of a generic Provisioning engine. So, we began working on a design for a new Provisioning engine, to be called Zero Touch Provisioning (ZTP), that could be used to help an outsourcer manage desktops and reduce helpdesk costs. We began by prototyping on the BizTalk Server 2004 beta. Then, we created a conceptual design and formal scope. We planned to ship a version with the BDD Solution team in conjunction with Zero Touch Install (ZTI) around Q2-2004. In Q4-2003, we took our grandiose plans to Redmond to talk with both the MIIS team and IDM Solutions team to integrate BizTalk with MIIS and provide more scenarios on the same engine. We were told "no thanks" by the MIIS team, they hoped to ship MIIS 2003 and then a workflow engine soon after, and "maybe" by the IDM Solutions team, who hoped to provide a workflow solution as well. We also talked with the BizTalk Server team, who was excited by our use of HWS, but we ended up not working with any of them. MS Services had a customer and a core scenario that matched a scenario from the BDD team, so we were still planning on publicly shipping. We worked on ZTP from Q4-2003 through Q1-2004 to deploy the alpha release at our customer in March 2004. After demonstrating the core functionality at a customer, we went back to the various product (MIIS, BizTalk, SMS) teams to discuss another public release vehicle by adding more scenarios. Ironically, we couldn't convince the product teams to invest in integration across our server platform. At this point, we needed funding (MS Services doesn't work for free, even for internal projects) and the BDD team began paying for 1 persons time. This allowed Brandon to stay focused on ZTP. I continued to work for free for a while and eventually got funding from another source within MS. Due to SP1 and OSD, the BDD team slipped to Q3-2004, so Brandon got some quality time to fix issues. In July 2004, it was decided that we'd demonstrate and launch ZTP (in beta) at the MS global training event. Brandon and I worked feverishly on a killer demo and mediocre hands on lab. We packed our small room and generally impressed (and confused) the audience. Now, we were publicly committed to shipping this thing with the BDD team. We'd already been working 12+ hour days for months, but from August to November, we stopped sleeping and worked a minimum of 16 hours per day, often working for 36 hours straight. Honestly, neither of us remember sleeping, but we must have. Thankfully, the BDD team slipped again to Q4-2004. Our district had won a sales award, so we both did take a few days vacation to Hawaii. We released ZTP build 2.0.225.0 on October 29th 2004. We made a couple small updates (defaults, setup, spelling) to release 2.0.225.0-E with the BDD team in November 2004. Then, I got to go to IT Forum to create a ZTP demo for Bill Gates to launch OSD, BDD, and ZTP. Since then, I've trained and assisted people around the world (from MCS, Premier, MS IT, partners, and customers).

ZTP was born because two guys from MS Services had the sheer will to make it happen (with the help of many people, like Eddie, Graham, Mike, and Tony along the way). Funnily, it's almost been a year since we released, and MIIS still hasn't shipped any workflow (2 years since our first conversation), HWS has become something else, and we have multiple customers around the world using ZTP in different capacities. However, I still can't convince our server product teams to invest in integration across our server platform using BizTalk. And, we still don't have MIIS integration as a free download. Different teams may try to take the credit for our vision and deviate from MS Services, but it started here first with a bold Services Director betting on two techie Consultants.

If you're using the .NET Framework and seem to have strange exceptions or hangs that you can't track and resolve, you need to consider the following .NET Framework 1.1 Hotfix Rollups (by querying support.microsoft.com for: framework 1.1 hotfix rollup post-service pack):