Partner Support Community
(Post dedicated to Nuri, Operations Manager for our delivery team in EMEA, and courtesy Sean Earp)
With the addition of PowerPoint Web App to SharePoint 2010, you can now view and edit PowerPoint presentations directly from within your browser. This technology has also been made available to consumers on services such as http://office.live.com/ and http://docs.com/.
In the past, it has been difficult to embed a PowerPoint document within a webpage, requiring workarounds such as saving the presentation as pictures, PDFs, or MHT documents. If you have a public presentation, it is now extremely easy to embed a PowerPoint deck on any web page, following the steps on the aptly named how to embed a PowerPoint presentation on a web page post.
Unfortunately, these steps do not work if your installation of PowerPoint Web App is local. The Share –> Embed option available from http://office.live.com is simply not present on SharePoint 2010.
So what to do if you want to embed an internal, private, or confidential PowerPoint presentation on an internal SharePoint page? Fortunately, it is possible to embed a presentation on a webpage without posting the presentation on a broadly available public site.
Step 1: Ensure that Office Web Apps have been installed and configured on SharePoint 2010. Those steps are out of scope for this article, but the official documentation should be all you need: Deploy Office Web Apps (Installed on SharePoint 2010 Products)
Step 2: Upload the PowerPoint to a document library
Step 3: Click on the PowerPoint Deck to open it in PowerPoint Web App. It will have a URL that looks like:
Don’t worry about writing down the URL. Unfortunately, you can’t paste it into a Page Viewer web part without getting an error message. So… a little magic to get the URL we need to embed our PowerPoint deck on our SharePoint Page.
Step 4: Open the Developer Tools in Internet Explorer (F12), and search for iframe.
Step 5: Copy the first result into your text editor of choice. The magic URL you need is the one within the src attribute.
Step 6: Delete everything except the part inside the quotes. Before the PowerPointFrame.aspx, add the relative URL to your site collection _layouts directory, and copy the whole URL into your clipboard.
Step 6: Go to the SharePoint Page you want to embed the PowerPoint into. Add a Page Viewer Web Part to the page. Open the tool pane for the web part,
Step 7: In the Page Viewer tool pane, paste in the URL, and optionally enter a height/width and chrome state for the PowerPoint Deck.
Step 8: Hit “OK” and be awed at how awesome it looks to have a fully functional PowerPoint deck embedded on your page. You can view the deck full screen by clicking “Start Slide Show”, you can change slides, view notes, click links, or click the “popout” button to have the deck open up in a popout window.
Super-secret-squirrel trick: If you want the deck to default to a slide other than the cover slide, click through to the slide you want, and then click the popout button in the top right of the PowerPoint Web App. The deck will be open to that slide in its own window.
Use the same Developer Tools trick from step 4, but this time search for &SlideId. You will see the URL has added two parameters… a slide ID and popout=1 (the URL will end with something like &SlideId=590&popout=1). You can guess what popout=1 does, and the SlideId is some sort of internal reference to the Slide ID (I have no idea how it is generated, but it doesn’t matter . My web app-fu will work just the same). Just copy the &SlideID=somenumber and paste it to the end of your URL in the Page Viewer web part, and now your web page will display the PowerPoint deck starting on whatever page you specified!
Office Web Apps technical library
(Post courtesy Iftekhar Hussain)
As you all know that SP1 for Windows Server 2008 R2 and Windows 7 just gone RTM adding two new virtualization capabilities: Dynamic Memory and RemoteFX
Let’s first understand these capabilities in details.
Dynamic Memory: An enhancement to Hyper-V R2, Dynamic Memory pools all the memory available on a physical host. Dynamic Memory then dynamically distributes available memory, as it is needed, to virtual machines running on that host. Then with Dynamic Memory Balancing, virtual machines will be able to receive new memory allocations, based on changes in workload, without a service interruption.
RemoteFX: Microsoft RemoteFX leverages the power of virtualized graphics resources and advanced codecs to recreate the fidelity of hardware-assisted graphics acceleration, including support for 3D content and Windows Aero, on a remote user’s device. This allows for a local-like, remote experience.
In the light of new features, service Pack 1 will also be released for VMM 2008 R2 to manage Dynamic Memory and RemoteFX on multiple Hyper V Servers from a single pane of glass.
Lets understand the requirements on your Hyper V hosts and VMs to be able to manage by VMM 2008 R2.
System Requirement for Manage Dynamic Memory:
RemoteFX Requirements on Hosts
RemoteFX requirements on VMs
VMM 2008 R2 SP1 now has settings to manage Dynamic Memory setting of VMs which are as follows:
To manage the RemoteFX , following settings have been added
Since RemoteFX requires you to have SLAT CPU and specific GPU and available GPU memmory, VMM 2008 R2 SP1 will also let you identify the following on the hosts.
1. CPU Supports SLAT
2. GPU and available Memory
3. Intelligent Placement
While creating a new VM or migrating a new VM from one host to another, VMM 2008 R2 SP1 added new check for Dynamic Memory and RemoteFX in the Intelligent placement.
4. Updates to Performance and Resource Optimization
PRO ties specific Operations Manager alerts to remediation actions in VMM, VMM moves a load-balance VMs in a cluster when CPU or Memory exceed a threshold. SP1 update to VMM PRO Pack a consider Current Memory utilization and not the fixed memory for DM VMs and matches it with the memory available on the other nodes.
How do I upgrade from SCVMM 2008 R2 to SP1?
Pretty simple, just 4 steps to upgrade
VMM 2008 R2 SP1 will take the virtualization management to a whole new level and is scheduled to be released within 30 days of SP1 released by the Windows Server Team. So we can expect it sometime next month.
I hope this post was of some help for those who are expecting VMM to be able to manage Dynamic Memory and RemoteFX on multiple hosts from a single console instead of managing it locally using Hyper V manager on each box.
If you have any further queries, please feel free to reach me
The User State Migration Tool (USMT) allows you to migrate user settings and data between computers during operating system deployment.
When deploying operating systems with System Center Configuration Manager 2007 (SCCM), you must use USMT functionalities whenever saving users’ settings and documents is a requirement.
In order to do so, USMT must be configured as a package within SCCM. This blog post shows how to create a package for USMT 4.0 which is required for Windows 7 deployments.
(Post courtesy Simone Pace)
In my first post: Capture a Windows 7 image from reference computer using Capture Media we saw how to capture a Windows 7 WIM image and how to make it available for SCCM to use.
We will use that image to upgrade a client computer’s operating system to Windows 7.
One of the steps that is usually required during an OS upgrade project is to keep user’s settings and data. User State Migration Tool will do the job for you but it must be correctly configured as an SCCM package in order to be used during our automated deployment process. USMT 4.0 is copied to the system during installation and setup of the Windows Automated Installation Kit (AIK) setup.
Note: Screenshots and computer names used in this article refers to a Virtual scenario running on a Hyper-V R2 host: All Servers are Windows 2008 R2 Enterprise servers. Domain: contoso.com Server CON-001 · SCCM with all required roles installed · SQL Server 2008 for SCCM database · Windows Automated Installation Kit 2.0 · WDS Transport Server role installed SCCM Primary Site: C01
Note: Screenshots and computer names used in this article refers to a Virtual scenario running on a Hyper-V R2 host:
All Servers are Windows 2008 R2 Enterprise servers.
1. Create the Package.
Create New Package and fill in the right information to correctly identify the package. Click Next.
On Data Source check “This package contains source files”, click set and select “Local drive on site server”, click browse and select the folder “C:\Program Files\Windows AIK\Tools\USMT”, click OK twice (this step requires WAIK 2.0 to be already installed). Click Next.
Leave the default settings and click Next on Data Access
Leave the default settings (recommended) or apply the required changes and click Next on Distribution Settings
The default settings on reporting page are just fine J. Click Next on Reporting
Check the security settings and change them if required, click Finish and complete the package creation wizard.
2. Distribute the package on DPs.
Right click on the package and select Manage Distribution Points
Skipping the Welcome page… Select “Copy the package to new distribution points” and click Next.
Select your Distribution Point(s) and complete the Manage Distribution Points Wizard
3. Check the package distribution results in Package Status
Once the package is installed in our Distribution Points, it is ready to be referenced by SCCM to capture and restore user’s data and settings during an Operating System Deployment process.
(post courtesy Natalia Efimsteva)
Office 2010 provides a better productivity experience than previous versions. Evaluating the compatibility of existing hardware, Office documents, add-ins, and line-of-business applications is an important part of planning an Office 2010 deployment.
In the first part of this post we will have quick overview of new compatibility toolkits provide by Microsoft, and in the second part focus on x64 platform compatibility.
Microsoft provides several tools, programs and guidance for compatibility assessment:
All compatibility areas are getting addressed by the full set of tools and programs:
Office 2010 ISV Application Compatibility Visibility Program
Office 2010 ISV Application Compatibility Visibility Program is new program which tracks independent software vendors who pledge that their products are compatible with Office 2010 (something like Windows 7 Logo program). OEAT (about which we will talk later) also uses this list to highlight known compatible add-ins and report them as compatible.
Office Migration Planning Manager
Office Migration Planning Manager is a collection of tools which provide detailed information regarding potential file format/document compatibility issues before migration. You can use the tools in OMPM to scan Office 97 through Office 2003 files for conversion issues or to convert older Office files into the Office 2010 file formats. OMPM checks file properties and contents to help you analyze the environment and determine any issues that you might experience converting from Microsoft Office versions 97 through 2003 file formats to Office 2010 file formats. And OMPM can macros for 32-bit versus 64-bit compatibility (new feature).
Assess the compatibility of Office documents for migration to Office 2010:
1. Create a database for OMPM where all aggregated and extracted information will be stored.
CreateDB.bat <SQL Server Name> <Database Name>
2. Specifying the Scanner Configuration.
Analyze offscan.ini configuration file.
3. Executing and verifying the scan.
4. Importing scan data into OMPM database.
ImportScans.bat <SQL Server Name> <Database Name> <File Path To Scan Report>
5. Analyze reports.
Open consolidated Access database which connected to SQL Server database which now contains scan data. In Issue Summary tab you can review the scan results issue summary results classified in Green, Yellow, and Red types.
In Scanned Files tab you can review the list of scanned files and you can find information about files which contains different issues (for example, embedded versions which are no longer supported). And you these issues must be addressed prior to conversion.
In Macro Summary tab you can review the list of scanned files with macros. The columns Function Issues indicate the count of the number of potential functional issues due to object model changes in the macro project. The x64 Function Issues column is the count of the macros with potential functional issues if used with 64 bit Excel. Problematic files must be examined in detail using the OCCI tool to determine the specific issues.
Office Environment Assessment Tool
Office Environment Assessment Tool is a comprehensive environment scanning tool. This tool assists a customer in the assessment phase of deployment. It identifies the following:
OEAT is a user-mode tool. This means that it cannot be run in a system context, with a system account, or as a service. Some of the information that OEAT collects requires administrative rights on the local computer. Therefore, the user account that runs OEAT must belong to the Administrators group on the local computer on which it is run.
Provide an initial compatibility assessment for Office Add-Ins:
1. Configure OEAT settings.
2. Copy OEAT.exe and Settings.xml to computes you are going to scan. Run scanning process.
3. Get reports after scan. Reports are compiled into Excel workbook.
4. Analyze results.
Open the AddinsNotShippedWithOffice sheet in the workbook.
Review the list of discovered add-ins. The Compatibility column indicates if the add-in is a known add-in in the Office TechNet vendor compatibility list. Partial Match indicates an add-in from that vendor was found but not the exact version matches. Focus on the add-ins with Partial and Unknown matches for follow-on research and testing in a productive deployment.
Office 2010 Compatibility Inspector Tool
Office 2010 Compatibility Inspector Tool compares existing (legacy) code against the Office 2010 object model by using a text search (patterns) for known properties and methods that have changed. The tool integrates with both Microsoft Visual Basic for Applications 7.0 (VBA 7) and Microsoft Visual Studio 2008. It includes a basic scanner where definitions and remediation links are updated from a central online location. It also generates a summary report and a details report. Compatibility Inspector also scans declaration statements for 64-bit compatibility.
You cannot use this tool to inspect code from Microsoft Outlook or Microsoft Access. However, you can use the tool to inspect Excel, PowerPoint, and Word code for interaction with the Outlook object model.
Identify code that maybe affected by object model changes: 32 bit Declare, ActiveX Controls, and external type libraries contained within an Excel, PowerPoint, or Word document:
1. Configuring the Trust Center to provide OCCI VBA Project access.
Excel → File → Options → Trust Center → Macro Settings → Trust access to the VBA project object model
2. Display the Developer tab.
Excel → File → Options → Customize Ribbon
3. Install the OCCI add-in.
4. Inspecting VBA code.
Open Excel file which contains macros. Developer tab → Inspect VBA Code → Inspect.
5. Analyze OCCI scan results.
Total lines scanned – total number of VBA code lines scanned in the document.
Total items found – total number of problematic items that the Inspector found in the code, including Declare statements to update, changed items, deprecated items, and items affected by design changes.
Deprecated items – items in the code that were removed from the object model, or are no longer supported in it. If your code is dependent on a deprecated item, you must rewrite that portion of the code.
Changed items – items in the code that use a command whose syntax has changed. If your code uses outdated syntax, you must update the code.
Redesigned items – items in the code whose syntax is the same and still exists, but whose updated design might yield unexpected results against your code. For example, formatting a particular text box might have changed because of new text services, and as a result, your code might create a text box, but the layout of the text in the box might be different from previous versions.
Declare statements – total number of Windows API statements detected in the VBA code and then updated for 64-bit compatibility by adding the PTRSAFE keyword.
The OCCI detailed report provides the same information as the summary dialog, but also much more specific information about the VBA Project.
The report includes:
OCCI writes a VBA code comment in an XML format above each line of code that contains an object model reference that matches a known change.
The presence of these comments does not necessarily mean that the line of code will cause an error or other issue. OCCI detects that there was a change, and is providing an indication the code contains a change. However, if during code testing problems occur, OCCI code comments provide indications of possible causes.
In analyzed Excel from the Developer tab click Visual Basic and select required code module.
Application Compatibility Guide includes different guidance and manuals which are available on MSDN and TechNet.
The Microsoft Office 2010 system is available in both 32-bit and 64-bit versions (new!). The 64-bit version enables you to work with much larger sets of data. This need is especially true when working with large numbers in Microsoft Excel 2010.
Data Execution Prevention
Microsoft Office 2010 has a new security feature, Data Execution Prevention (DEP, read Data Execution Prevention in Office 2010), which prevents badly-written code from running that can harm your computer. When an add-in that is not designed to function in a DEP-enabled environment tries to run, the Office program that you are using stops working (crashes), and an error message appears after the program restarts. DEP cannot be disabled on 64-bit.
Microsoft Visual Basic for Applications 7.0 (VBA 7)
With the introduction of the new 64-bit version of Microsoft Office 2010, a new version of Microsoft Visual Basic for Applications (VBA), known as Microsoft Visual Basic for Applications 7.0 (VBA 7), is being released to work with both 32-bit and 64-bit applications.
In VBA 7, you must update existing Windows Application Programming Interface (API) statements (Declare statements) to work with the 64-bit version. Additionally, you must update address pointers and display window handles in user-defined types that are used by these statements. This is discussed in more detail in this article as well as compatibility issues between the 32-bit and 64-bit versions of Office 2010 and suggested solutions.
COM objects and ActiveX
You need to update COM objects or recompile them. Native 64-bit processes in Office 2010 cannot load 32-bit binaries. This includes the common controls of MSComCtl (TabStrip, Toolbar, StatusBar, ProgressBar, TreeView, ListViews, ImageList, Slider, ImageComboBox) and the controls of MSComCt2 (Animation, UpDown, MonthView, DateTimePicker, FlatScrollBar).These controls were installed by previous versions of Microsoft Office and are installed by 32-bit Office 2010. An alternative must be found for existing Microsoft Office VBA solutions that utilize these controls when the code is migrated to 64-bit Office 2010. 64-bit Office 2010 does not provide 64-bit versions of the Common Controls.
Office 2010 32-bit and 64-bit in SxS mode
Office 2010 64-bit cannot be installed SxS with Office 2010 32-bit or previous versions of Office. Please use application virtualization if it is a possible path for you.
System Center Configuration Manager 2007 allows you to customize your automated deployment tasks by using Task Sequences. Task Sequences provide the mechanism for performing multiple steps or tasks on a client computer at the command-line level without requiring user intervention. The power of task sequences lies in their flexibility and administrators can use these to configure client settings, distribute software, update drivers, edit user states, and of course automate operating system deployments.
Welcome to the third post about Operating System Deployment using System Center Configuration Manager 2007.
(post courtesy Simone Pace)
After we generated our Windows 7 WIM image (see my post Capture a Windows 7 image form reference computer using Capture Media), we prepared a package to allow USMT (User State Migration Tool) to collect user’s data and settings in the post User State Migration Package creation for Operating System Deployment).
Now we have all the pieces we need to create our Task Sequence that will be executed by the clients we are going to “upgrade” to Windows 7.
Testing lab description screenshots and computer names used in this article refers to a Virtual scenario running on a Hyper-V R2 host:
1. Start the Task Sequence Wizard
Note Whatever you write in the comment field will be seen by users when they seek for details in the upgrade notification. This is useful to inform users about what is going to happen to their computers, for example you could write something like: “This program will install Windows 7 on your computer keeping your document and settings”. You can add or change the comment any time after you created the TS. Click Next.
Note depending on how you captured the WIM image you can have more than one image in it. As I used the SCCM 2007 OSD Capture CD on a PC where Windows 7 was manually installed, it captured not only the partition where Windows was installed (2-2), but also the “bitlocker enablement” 100MB boot partition (1-1), and stored both partitions as images in the WIM file.
To install Windows 7 files, we only need the partition 2-2 from this package.
Tip By opening the Image Package properties, you can browse the images it contains to see which one has the Operating System bits in it.
The OS partition is the image that has information next to the fields "OS version", "Architecture" and the appropriate size :).
Note We are saving user settings on a State Migration point which is a Site System role installed and configured with a network Share.
Note: Per-system unattended program is selected by default.
2. Edit the Task Sequence
We created our Task Sequence starting from a template and going step-by-step through the Wizard. In order to be sure that everything goes as we want, we need to make some adjustment to the newly created TS. Editing is also a good way to adapt your TS to changes in your deployment strategy.
The boot partition is set to be 300Mb in size and to be quick formatted in NTFS. Make sure to check the flag Make this the boot partition. Also note the Variable set to BOOTPART. This variable gives us the option to reference this partition when we will indicate where to install OS system files later in the TS.
3. Go to the Apply Operating System node and reference the destination partition we set in the previous step by selecting Logical drive letter stored in a variable from the drop down list and type in the name: SYSPART
Note: At the “Setup Windows and ConfigMgr” task, the OSD Task Sequence will figure what type of Boot Manager is needed (XP/2003 vs. Vista/2008/Win7) based on what OS was deployed during the "Apply Operating System" task, and then install it on the appropriate partition. Whichever partition/volume is marked as “Make this the boot partition” in the “Format and Partition Disk” task, is determined to be the partition where the Boot Manager and boot files will be installed.
· Change the windows registration and licensing settings as desired.
· We are now ready to advertise our TS and start upgrading computers.