PowerShell: Backup your running Hyper-V Virtual Machines

If your like every one else including me its been a complete drag attempting to get clients to allow you to shut down Virtual Machines that are in production to allow you to back them up.  Windows Server 2012 R2 (a free upgrade of Windows Server 2012) can be upgraded remotely using RDP without too much risk. I competed 4 Hyper-V Hosts Friday night without issue. The upgraded is pretty fast but we had to migrate the running VMs prior to the upgrade, and it too about an hour to bring the  the new 2012 R2 Hyper-V hosts current with all Security and Hot Fixes (132 patches) .

image

 

Set-VMBackup.ps1

We have the backups  using task scheduler, since we have multiple Hyper-V hosts, we created the schedule once then exported to xml, and imported the task on all additional Hyper-V Hosts.

 

 

Also, since the VMs rarely change we keep two backups locally and the rest are moved to the SAN in this case a NetApp for two weeks and copied to tape. Note: You only need to modify the drive and root folder, if the folder does not exist it will be created.

PowerShell Script

<# Set-VMBackup.ps1 #>

#Get date string
$timestamp = Get-Date -UFormat "%Y%m%d"

#Change the Drive / Folder where the exports should be stored
$BackupPath = “D:\VMBackup\$timestamp#Export running VMs to Export path
GET-VM | where {$_.state -eq ‘running’} | Export-VM -Path $BackupPath

Download http://1drv.ms/1PPFoUg

 

Ivan

PowerShell: Upgrade WAC – your Office Web Apps Farm

Like most folks who upgrade their SharePoint 2013 farms after they have applied the latest SharePoint 2013 CUs to the SharePoint side of the environment they will usually still have 2 WAC servers and at least 3 WFM servers left to apply and configure updates. This may depend on release of the updates as the Service Bus and Workflow manager updates do not coincide with the monthly delivery of SharePoint 2013 CUs.

image

 

Upgrade-WAC.ps1

The reason for this post is to make it easy for me (not to forget) updating the WAC Servers / Office Web App Farm. Updating the Office Web App farm is somewhat unique in that you remove the farm prior to the installing the CU then create a new farm after the cumulative update installed


 

 

 

 

PowerShell Script

# Update-WAC.ps1
# Add July 2015 CU

Import-Module -Name OfficeWebApps 

# Review the Current State of the Office Web App Environment
Get-OfficeWebAppsFarm 
Get-OfficeWebAppsHost 
Get-OfficeWebAppsMachine 
cmd /c pause 

# Remove OfficeWebAppMachine prior to installing Cumulative Update
Remove-OfficeWebAppsMachine
cmd /c pause

# Install the Cummulative Update while paused

# Configure Office WebApp Farm after installing the updates
# If using HTTP remove comment below
# New-OfficeWebAppsFarm -InternalURL "http://wac.contoso.com" -AllowHTTP -EditingEnabled

New-OfficeWebAppsFarm -InternalURL "https://wac.contoso.com" -ExternalURL "https://wac.contoso.com" -CertificateName "wac.contoso.com" -EditingEnabled
cmd /c pause

# Open IE to test and ensure the New OfficeWebApps Farm is configured
$ie = New-Object -ComObject InternetExplorer.Application
$ie.Navigate("https://wac.contoso.com/hosting/discovery.ashx")
$ie.Visible = $true
If successful your browser will open and will look the example below

SNAGHTML39a1ce2e

 

Download http://1drv.ms/1JCmcKm

 

Ivan

Metalogix Content Matrix 7.3.x – Bugs

 

SharePoint 2013 and Metalogix Content Matrix

SharePoint is mission-critical and users demand availability. Content Matrix allows you to migrate SharePoint by site collection, site, list, library, business unit, or department with zero downtime. Run old and new farms in parallel and test and re-arrange as often needed. Along with the Re-Organizer feature empowers your site collection owners and users, to manage SharePoint sites, content and metadata on an ongoing basis to keep in sync with business needs. All of my clients love this tool as it makes their environments more flexible and now with Re-Organizer we are enabling the site owners to more easily manage their site structure.

 

 

 

 

Error on Installation of Content Matrix 7.3.0002

During the installation of the Online edition of Content Matrix version 7.3.0002 while installing Metalogix Extensions Web Services you will see the error "MD5 check failed for the current file to be staged, the file may be corrupt" in the screenshot to the left. However, the installation will continue and complete. Also, if you go to the location in your AppData Folder and copy the "Metalogix SharePoint Extensions Web Service Setup.msi" it will run locally without any issues. The error appears to be related to the msi not matching the online manifest

 

 

 

 

Error Copying List Views Content Matrix 7.3.xxxx

Unfortunately, the installation error is not the only issue. The infamous "Object Reference not set to an instance of an object" error occurs when you attempt to copy list views. However, if you copy the complete list all views are included in the copy. In looking at the error details it appears to be caused by a dialog box, this makes sense as it never creates the job or writes to any log.

 

 

 

 

 

image[14]

 

Error Copying Sites Lists or Library’s  Content Matrix Organizer 7.3.xxxx

The last symptom was when attempting to copy / move anything  using the Reorganize from the Widget Drop Down or the Ribbon of the list…

 

We initially found and reported these errors on 12/18/2015..

At first we thought incorrectly the error only occurred after an upgrade from an earlier version of Content Matrix, after further testing we found the issues existed in all 7.3.x versions whether installed as part of an upgrade or installed in a pristine environment. As always Metalogix Content Matrix is our favorite tool for SharePoint Migrations whether on-prem or online and Metalogix support is very helpful.  The only resolution at this time is to revert to a previous version Metalogix Content Matrix version 7.2.0017

 

 

 

 

 

Ivan

Bastille Day – July 14th, 2015 Migration is worth it!!

Windows Server 2003 & 2003 R2 Support is ending July 14, 2015

Bastille Day, Symbol of the French Revolution

What does end of support mean for you? After July 14, Microsoft will no longer issue security updates for any version of Windows Server 2003:

  • If you are still running Windows Server 2003 , you need to take steps NOW to plan and execute a migration strategy to protect your infrastructure.
  • By migrating to Windows Server 2012 R2, Microsoft Azure or Office 365, you can achieve concrete benefits, including improved performance, reduced maintenance requirements, and increased agility and speed of response to the business.
  • Extended support for Windows Server 2003 will end on July 14, 2015, and customers are once again looking at the final months of a generous Windows product support cycle. Recommendations for customers using Windows Server 2003 include the following:
  • Customers that go beyond the termination of extended support place themselves at risks and potentially in a regulatory noncompliance situation. Even if regulatory compliance is not a concern, the security improvements that Windows Server 2012 R2 provides are worth adopting if just to help defend against industrial espionage.

 Key issues if you are still supporting Windows Server 2003 after July 14th 2015:

  • Lack of patches/updates/non-security fixes. No-cost, non-security-related update support terminated on July 13, 2010. However, support for non-security-related updates was available on a for-fee basis to customers that felt it was important to continue to have access to fixes that could help their system run optimally and perform well.
  • Elimination of security fixes. Customers see security fixes as being among the most critical fixes for their installed servers. These fixes will no longer be delivered to customers for their Windows Server 2003 servers, regardless of how severe a given issue may be. This may be less of a problem with many aging Windows Server 2003 applications, mainly because the applications still in use are increasingly likely to be inward facing rather than outward facing.
  • Lack of support. Customers no longer have the ability to contact Microsoft for technical support in the event of a server problem. This becomes particularly important when a system experiences an outage and customers are unable to restore the system and recover data and applications from the stalled machine.
  • Application support challenges. Application ISVs dislike having a complex support matrix and typically support current versions along with a finite number of earlier editions of the product. For most ISVs, an 11 -year-old application is probably already past its rational support life cycle, and in most cases, these application ISVs are about to discontinue or have already discontinued support for aging operating system environments such as Windows Server 2003.

Regulatory Compliance :

  • Customers in regulated industries or handling regulated data, including healthcare and payment card industry (PCI) data, may find that they are out of compliance, which could mean fines or being cut off from key trading partners that seek to protect their own regulatory compliance status.
  • Inability to leverage modern cloud options from Microsoft and other vendors. Windows Server 2003 can run on virtually every hypervisor in the market, but that does not mean it is an equal player in these modern deployment scenarios. For example, Windows Server 2003 installations cannot be re-hosted in a Microsoft Azure environment, unless it is a 64-bit image, but the vast majority of Windows Server 2003 installations are 32-bit solutions. So even if customers bring the 32-bit image to the Azure cloud, they cannot continue using that operating system instance. When spinning up new infrastructure-as-a-service (IaaS) instances in Azure, Microsoft provides catalog images only for 64-bit instances of Windows Server 2012 R2.

Bottom Line:

Security vulnerabilities could arise for which no protection is possible. Attackers who exploit these openings could gain control of systems based on Windows Server 2003. Then use the compromised system to launch attacks from within the data center against other, newer systems to capture and relay data from the network to the attacker outside and introduce false transactions or tamper with legitimate business activities. If such an attack were to take place, it may be impossible or impractical to stop it from succeeding and from being repeated, since the code vulnerability inside the OS will not be patched. Business functions dependent upon the system running under Windows Server 2003 may be unexpectedly subject to complete loss of access to the functionality of the system if it has to be shut down due to compromise. Alternatively, lack of viable alternatives for the business function may dictate that the system remain in operation despite compromises, thus endangering other systems that are not based on Windows Server 2003.

Wow 13 Years who would have thought…

If you have NOT decommissioned your Windows Server 2003 Servers then you should purchase an Extended Sup[port agreement for these servers and actively be in the process of moving to new Hardware and Software… You can use the Windows Server 2003 Migration Planning Assistant which will walk you through a migration assessment and help you choose a Microsoft partner if you need help in the migration and decommissioning of your old hardware.

 

Ivan

First Ever Live Office Bug Bash To Be Held On July 15, 2015 Report Bugs And Win Cool Prizes From the Microsoft Office Team

image

Mark your calendar for July 15 from 10am – 1pm PDT.

You can win Power chargers, USB slap bands, pre-paid run-me tags, universal USB adaptors, t-shirts, hats, stylus pens, Office O365 Pro Plus subscriptions with 25 seats, and lots more by reporting bugs.

GETTING STARTED

Join the public O365 Network

Go to https://www.yammer.com/itpronetwork#/Threads/index?type=algo  and join the O365 Network

After Tuesday, July 14 search for the “Office 16 Bug Bash – July 15” Group. (NOTE: this group will not be public until after this date and requests will not be approved)

 

Beginning on July 15 @ 10am PDT, post your issue using one of the appropriate hashtags (aka Topics) below:

  • Outlook, Excel, Word, PowerPoint, OneNote, Access, Visio, Project, Publisher, Setup, Localization, Install, General, Activation

Custom Testing Activities

Real Time Co-Authoring in Word – Load Testing – 10:00 – 1:00 pm PDT

This feature enables customers who are collaborating on a document to see text changes others are making as well as the location of their cursor within the document. Changes are displayed automatically as people use and update the document. This capability will be available when working in documents stored on OneDrive for Business and Office 365 SharePoint sites.

Localization Testing for European & Middle Eastern Languages. 10:00 – 1:00 pm PDT  and 4:00 – 6:00 pm PDT

Do you use localized versions of Office 16? Do you feel the language quality of the latest builds is good or do you feel it needs some improvement? Well now is your chance to let us know. You will be able to report localization issues in Office 16 for your language so that we can address them before it ships.

All we need during this time is for you to give us the following information:

  1. Office Product
  2. Office Version
  3. Steps to reproduce the issue
  4. Screenshot(s) of the problem
  5. Current offending translation
  6. Suggested improved translation

HOUSE RULES

  1. This is focused on bugs only. If you have already reported an issue and it’s been closed as “Won’t Fix” or “By Design” do not report it again at this event.
  2. Each post/issue must be tagged (aka Topics) with at least one Topic (See Getting Started)
  3. Create a new thread for each issue
  4. DO NOT respond to a thread unless you are adding relevant information to that specific issue
  5. DO NOT initiate any private IMs with MS staff. We will get to your post as soon as possible.
  6. General forum rules and etiquette apply. Please play nice in the sandbox or we’ll have to send a note home to your mother.

FAQ

Q: Who can join this Bug Bash?

A: Anyone with a valid Office 365 subscription that is running the Office 16 Preview bits. Click here to install the preview.

Q: Is this event under NDA or other disclosure restrictions?

A: No.

Q: Can I submit Android, Universal, Mac, or phone issues during this event?

A: No, this event is focused strictly on the desktop bits.

Q: How do I win some of the cool prizes?

A: Find and report a great bug during the bash. Prizes will be awarded based on severity and impact of the issues as determined by Microsoft staff. Prizes will only be awarded during the hours of the event.

Q: What are some of the cool prizes I can win?

A: Power chargers, USB slap bands, pre-paid run-me tags, universal USB adaptors, t-shirts, hats, stylus pens, Office O365 Pro Plus subscriptions with 25 seats, and lots more great stuff!

 

See ya onsite!!

 

Ivan

SharePoint 2013 Unable to Open Documents from Ribbon when WOPI is Configured and Library Default open behavior for browser-enabled documents is Open in the client application

It appears to be an IE issue when clicking on the New Document Drop down from the ribbon using fiddler4 there are not any results returned, probably jscript or jquery … I am running IE11 and I have tested IE10 which exhibits the same behavior. I haven’t tested on earlier versions yet.

However, if you open with Mozilla the Microsoft Office is blocked until you Allow Mozilla to open Office Documents and then Default open behavior for browser-enabled documents works as expected. In other words when the library is set to open ion the browser (via WOPI) the documents open in the browser, when set to open in the client application, the docs open in the client as expected..

1. Click On Allow

Doc1_1-57-50

 

2. Then choose to Allow remember

Doc2_2-00-55

3. Then choose OK,

Doc3_2-02-20

 

4. Click on New Document one more time to open from the ribbon

Doc4_2-05-18

 

Note: this only occurs if you have WAC installed and configured WOPI with SharePoint. Also, you only have to go to library settings to set the Default open behavior for browser-enabled documents: to Open in the client application, you don’t have to set the site collection… I will resolve as time permits

 

Cheers,

Ivan

Orange County SharePoint User Group (OCSPUG) Site has changed

image

Tim and I were talking with the folks from Microsoft today (Sal, Grant and Antoni) discussing the upcoming OCSPUG when I noticed the OCSPUG.org site was down.

 

Also, thanks to Microsoft they have generously provided us their  South Coast Plaza Store presentation area to hold the monthly events…

Since all of this is going on I thought it would be a great idea to make sure everyone knew about the new the new Orange County SharePoint User Group Site #OCSPUG  http://www.meetup.com/OC-SharePoint-User-Group-OCSPUG and to ask you guys to check it out, and register as an OC SharePoint Rockstar. This will help all of us keep up with the current SharePoint stuff and answer any questions you may have in your environments that might keep you from banging your head against the wall too much. All of that said, as you guys know if you have an emergency of any type and need some please reach out as we can usually save you a lot of time and effort. If its not that big a deal and can wait 24 hours just send me an email and I will generally always reply with 24 hours..

Now for the sales pitch right after you register for OCSPUG you need to register for SPSLA

SNAGHTML2694f289

 

This event is for  all of you SharePoint administrators, architects, developers, designers, analysts, teachers, students, content managers, digital librarians, dbas, business users and other folks that work with Microsoft SharePoint Technologies.

This is our 5th SharePoint Saturday event in Los Angeles Event and will be on August 8th 2015 at Santa Monica College

 

 

 

Directions

Map picture

When

August 8th, 2015
830am-530pm

WHERE

Santa Monica College

1900 Pico Blvd.

Santa Monica, CA 90403

http://www.spsevents.org/city/la/la2015

Follow us on Twitter #SPSLA, #OCSPUG and we look forward to hanging out and answering and having fun with SharePoint

 

Cheers,

Ivan

clip_image001 clip_image002 clip_image003 clip_image004 clip_image005 clip_image006

 

SHAREPOINT SATURDAY – LOS ANGELES 2015 – ASK THE EXPERTS

image 

 

 

 

 

 

 

 

ONLY

41 DAYS UNTIL

WE GET

TO HANG

OUT WITH

FRIENDS

AND

ASK THE EXPERTS

 

 

 

 

 

 

 

 

 

 

See ya there!!!

Call to Action: Windows 10 Client FEATURE REQUEST: Please Add De-Duplication Feature

This is something that IT Pros and Devs should readily understand. However, it can save all users time and money..

As an example: I run Windows Server 2012 R2 on my Laptop  where I have 2 1tb SSD drives (they are a lot cheaper now) so I can natively run SharePoint instead of having to use several VMs. When I have Windows Server 2012 R2 Installed I use De-Duplication and it enables me to save 436GB of disk space by keeping a single version of the file on the data drive while creating pointers to the file in every location where a duplicate exists. If you do a lot of SharePoint development you end up with a lot of Hives so that you can easily start up a replica of your clients environment. Since I can only have two hard drives on my laptop and I am swapping out the DVD player to so. De-Duplication is a life saver, it allows me to store twice the amount of data as the disk would normally hold. if I then install a Desktop OS on my laptop I have to move my second drive to a server and copy the files off as they have been deduplicated and I would have been unable to open them on using the Windows 10 Client ,

image

The Server community has enjoyed DeDuplication since Windows Server 2012 in an Operating System but all SANs of all manufactures have this feature build in (too bad they don’t fit in your laptop bag). This is a hard drive  storage technology that should be made available in every OS not just  Server OSs. The really stupid part is that we can copy the features from the Windows Server OS and enable them on Windows 8, 8.1, and now 10. However, I really like to keep my systems as pristine as possible which is difficult enough when developing software..

 

If your running Windows 10 like me your probably running build 10130,  then complete the following steps to ask Microsoft to include this feature in Windows 10 Client OS

SNAGHTML4d24796[6]

1. Open Search or hit  the Windows key and type  feedback, then click on Windows feedback to Open the feedback app

2. Click on Files, Folders, and Online Storage. and type in dedup into the search bar

3. You will find 5/6 of people requesting de-duplication to be added to the Windows !0 Client OS, please Click UpVote at the bottom of each request

image

 

It is NOT a LUXURY to have De-Duplication on Windows 10 Client OS is a necessity as we can only fit 2 drives in as laptop and when you run multiple VMs to help people learn  software development skills. I cant really imagine why it would not be added to the Windows 10 Client OS.

 

Ivan

Embed a PowerPoint Presentation into a SharePoint 2013 Page with Multiple Farms

It seems like everyone NothingButSharePoint and Microsoft Office and Microsoft Bogs states that you can not embed unless your using Office 365 (this may have been due to using SharePoint 2010). There are many more post and articles that require you to use Onedrive.. There are probably many better ways to sharing Content using WAC with multiple farms and SharePoint On-Prem and I would enjoy hearing about how you have solved this issue

Embed a PowerPoint Presentation from a source SharePoint Farm and render the presentation in a target SharePoint Farm using CEWP

clip_image001

1. Go to http://focalpoint.cotoso.com and search for PPTX

2. Use the Drop Down, Choose embedded information, and Copy All

3. Go to http://learning.fabricam.com

5. Add Content Editor WebPart

clip_image002

6. Click Inside the WebPart Choose the Orange Insert, Click Embed Code

clip_image003

7. Insert (Paste CTRL+V) the Code you copied from http://focalpoint.contoso.com

SNAGHTML159a25c

8. Then Click the Insert button,

9. Next Edit the WebPart, and change the Width to 540px, then click OK

SNAGHTML15d48fe

10. Click Check-in, then Publish this Draft

SNAGHTML15f8f54

Note: The Site Collection Feature – Cross-Farm Site Permissions is activated on both Farms, the cross-farm site permissions feature to allow internal SharePoint applications to access websites across farms.

 

Ivan

« Previous PageNext Page »