Need assistance with ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH

I have tried resolution 2 but that did not work. When I try resolution 1 I get a Unrecognized argument error.. I am certain I am not formatting the command correctly and would appreciate any assistance. My source server is named HABSERVER and my destination server is named NC-USS-APP1. I was able to successfully create a package using the Web Tools but I can't bring that package into my new server.

.\msdeploy.exe verb:sync -Source:package=f:\iso\oldweb.zip,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2 -dest:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2,computername=NC-USS-APP1 -whatif > msdeploysync.log

I am getting this error...

.\msdeploy.exe : Error: Unrecognized argument '"-source:package=f:\iso\oldweb.zip
machineconfig32.netfxversion=2 machineconfig64.netfxversion=2 rootwebconfig32.netfxversion=2
rootwebconfig64.netfxversion=2"'. All arguments must begin with "-".
At line:1 char:1
+ .\msdeploy.exe -verb:sync -source:package=f:\iso\oldweb.zip,machineconfig32.netf ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Error: Unrecogn...begin with "-".:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError

Error count: 1.

ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH

1. Use the netFxVersion provider setting to tell Web Deploy exactly which .Net settings to migrate. Here is a command line example which forces Web Deploy to sync .Net 2.0 settings:

   msdeploy.exe -verb:sync -source:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2 -dest:webserver,machineconfig32.netfxversion=2,machineconfig64.netfxversion=2,rootwebconfig32.netfxversion=2,rootwebconfig64.netfxversion=2,computername=destServername

2. Run Web Deploy in the same version of .Net between client and server. On the client side, you can change the ordering of the supportedRuntime version element in the "%programfiles%\IIS\Microsoft Web Deploy V3\msdeploy.exe.config" file for the version of .Net that is specified first (see gacInstall provider for an example of this). This will indicate the version of .Net that will be loaded, assuming it is installed on your system. On the server side, you can do the same for "%programfiles%\IIS\microsoft web deploy\msdepsvc.exe.config". If you modify this file, make sure to restart the Web Deployment Agent Service (net stop msdepsvc & net start msdepsvc).