Installing Features on Demand through Powerschell contains a bug. You may see “failure to download files”, “cannot download”, or errors like “0x800F0954” or file not found.
To Solve that I created I powerschell script to run the install twice: featuresondemand.ps1
Version 3.10 (February, 2018)
– Upgraded RVTools solution to Visual Studio 2017
– Upgraded RVTools to .Net Framework version 4.6.1
– Upgraded Log4net to version 2.0.8, Waffle.AD to version 1.8.3
and NPOI to version 2.3.0
– Connection error when TLSv1.0 and TLSv1.1 are disabled and only TLSv1.2 is
enabled is solved by using .Net Framework 4.6.1
– vInfo tab page new columns: The latency-sensitivity setting of the virtual
machine, Change Block Tracking (CBT) and disk.EnableUUID values
– vDisk tab page new columns: SCSI label, unit number and sharedBus
– vHost tab page new columns: Assigned License(s), ATS heartbeat, ATS locking
values. 0 = disabled 1 = enabled, Host Power Policy shortname, CPU Power
Management current policy and CPU power hardware support
– When Export to xlsx is executed a metadata worksheet with version number of
RVTools and date time stamp is added to the output xlsx file
– All columns in the RVTools export xlsx file(s) now have a filter
– When export to csv newline characters are replaced by spaces
– When started from cli and login fails an error message and login box was
displayed. Now RVTools will exit with exit code -1, without showing the error
message and login form.
– Added an example PowerShell script with which you can merge RVTools export
xlsx files
– Added a example PowerShell script to start Export all to xlsx for multiple vCenters
– vDatastore tab page: For NFS datastores the address column is now filled with
remote host and path info
– vDatastore tab page new columns: Datastore Cluster Name, Cluster capacity and
Cluster free space
– The upper limit on the Health check for number of VMs on a datastore is now
9999
– vHealth tab page: new column “message type” which can be used as a filter in
Excel
– vHealth tab page: hbrdisk.RDID files are no longer reported as possible zombie
files
– vHealth tab page: low disk space messages no also show the free space in MB.
– All tab pages: Refresh or auto-refresh will respect your sort order
– CLI export2xls parameters changed to export2xlsx (old parameter will still work)
– Bug Fix: invalid “Horizontal Alignment” value in xlsx style sheet.
– Bug Fix: Calculation of total snapshot size was not always correct
– Bug Fix: Child snapshot hierarchy was not always correct
– Default installation directory is changed to C:\Program Files
(x86)\RobWare\RVTools without the version number
The Microsoft Deployment Toolkit (MDT), build 8450, is now available on the Microsoft Download Center. This update supports the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1709, available on the Microsoft Hardware Dev Center(adksetup.exe file version 10.1.16299.15).
Here is a summary of the significant changes in this build of MDT:
Supported configuration updates
Windows ADK for Windows 10, version 1709
Windows 10, version 1709
Configuration Manager, version 1710
Quality updates (titles of bug fixes)
Win10 Sideloaded App dependencies and license not installed
CaptureOnly task sequence doesn’t allow capturing an image
Error received when starting an MDT task sequence: Invalid DeploymentType value “” specified. The deployment will not proceed
ZTIMoveStateStore looks for the state store folder in the wrong location causing it to fail to move it
xml contains a simple typo that caused undesirable behavior
Install Roles & Features doesn’t work for Windows Server 2016 IIS Management Console feature
Browsing for OS images in the upgrade task sequence does not work when using folders
MDT tool improperly provisions the TPM into a Reduced Functionality State (see KB 4018657 for more information)
Updates to ZTIGather chassis type detection logic
Upgrade OS step leaves behind SetupComplete.cmd, breaking future deployments
Includes updated Configuration Manager task sequence binaries
On April 11, 2017, Exchange Server 2007 will reach End of Life. If you haven’t already begun your migration from Exchange 2007 to Office 365 or Exchange 2016, you need to start planning now.
End of life means that Microsoft will no longer provide the following for Exchange 2007:
Free or paid assisted support (including custom support agreements)
Bug fixes for issues that are discovered and that may impact the stability and usability of the server
Security fixes for vulnerabilities that are discovered and that may make the server vulnerable to security breaches
Time zone updates
Your installation of Exchange 2007 will continue to run after this date. However, because of the changes listed above, we strongly recommend that you migrate from Exchange 2007 as soon as possible.
To learn about your options for migrating from Exchange 2007 to Office 365 or a newer version of Exchange Server, check out Exchange 2007 End of Life Roadmap.
If you’re a customer who uses Azure Active Directory Connect, you’ll want to know that Microsoft just released version 1.1.343.0, which adds support for Windows Server 2016 and SQL Server 2016 and fixes some bugs.
Improvements: – Added support for installing Azure AD Connect on Windows Server 2016 standard or better. – Added support for using SQL Server 2016 as the remote database for Azure AD Connect. – Added support for managing AD FS 2016 using Azure AD Connect.
Fixed issues: – Sometimes, installing Azure AD Connect fails because it is unable to create a local service account whose password meets the level of complexity specified by the organization’s password policy. – Fixed an issue where join rules are not re-evaluated when an object in the connector space simultaneously becomes out-of-scope for one join rule and become in-scope for another. This can happen if you have two or more join rules whose join conditions are mutually exclusive. – Fixed an issue where inbound synchronization rules (from Azure AD) which do not contain join rules are not processed if they have lower precedence values than those containing join rules.
The Microsoft Deployment Toolkit (MDT), build 8443, is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607, available on the Microsoft Hardware Dev Center (adksetup.exe file version 10.1.14393.0).
You may notice that we are not tagging this release with a year or update version. To better align with the current branches of Windows 10 and Configuration Manager, and to simplify the branding and release process, we are now just referring to it as the “Microsoft Deployment Toolkit”, using the build number to distinguish each release. This is not necessarily a “current branch” of MDT; we are committed to updating MDT as needed with revisions to Windows, the Windows ADK, and Configuration Manager.
Here is a summary of the significant changes in this build of MDT:
Supported configuration updates
Windows ADK for Windows 10, version 1607
Windows 10, version 1607
Windows Server 2016
Configuration Manager, version 1606
Quality updates
Deployment Wizard scaling on high DPI devices
Johan’s “uber bug” for computer replace scenario
Multiple fixes for the Windows 10 in-place upgrade scenario
Several fixes to Configure ADDS step
Removed imagex/ocsetup dependencies, rely solely on DISM
Includes the latest Configuration Manager task sequence binaries (version 1606)
RVTools is a windows .NET 2.0 application which uses the VI SDK to display information about your virtual machines and ESX hosts. Interacting with VirtualCenter. RVTools is able to list information about VMs, CPU, Memory, Disks, Partitions, Network, Floppy drives, CD drives, Snapshots, VMware tools, Resource pools, Clusters, ESX hosts, HBAs, Nics, Switches, Ports, Distributed Switches, Distributed Ports, Service consoles, VM Kernels, Datastores, Multipath info and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to update the VMware Tools installed inside each virtual machine to the latest version. Version 3.8 (March, 2016)
VI SDK reference changed from 5.5 to 6.0
on vInfo tab page new field: ChangeVersion unique identifier for a given version of the configuration
on vInfo tab page new field: HA VM Monitoring status
on vInfo tab page new fields: Number of supported monitors and Video RAM in KB.
on vInfo tab page new field: Config status.
Config issues are visible on the vHealth tab page
on vInfo tab page new field: OS according to the VMware Tools
on vTools tab page new fields: App state, App heartbeat status and Kernel crash state
on vTools tab page new fields: Operations availability, State change support and
Interactive Guest Operations availability
on vHost tab page new field: NTPD running state.
NTP issues are visible on the vHealth tab page
on vHost tab page new field: Config status.
Config issues are visible on the vHealth tab page
on vCluster tab page new field: Config status.
Config issues are visible on the vHealth tab page
on vDatastore tab page new field: Config status.
Config issues are visible on the vHealth tab page
on vSC+VMK tab page new fields: IP 6 Address and IP 6 Gateway
all VM related tab pages now have a VM Object ID and VM UUID columnsall VM related tab pages now have powerstate and template columns
all tab pages. Now have a vCenter UUID column (= unique identifier for a vCenterServer)
all VM related tab pages. The Custom Attributes columns are now ordered alphabetically
all tab pages. A select is now a full row select so it is easier to follow the information across many columns
bug fix: Refresh data issue on vRP and vCluster tab pages solved
bug fix: Filter issue on vCluster tab page solved
bug fix: On vInfo tab page the HA information was not filled with cluster default values
bug fix: Content Libraries vmdk files are no longer reported as possible zombie files
bug fix: msi installer sometimes installs RVTools in root of c:\ drive. This is solved now.
News of a bug with Exchange Server 2016 Cumulative Update 1 has emerged, with some customers running Exchange 2016 Edge Transport servers finding that the Edge server rejects emails sent to valid email addresses.
Edge Transport servers can reject mail sent to valid recipients Exchange 2016 Edge Transport servers may reject messages sent to valid internal recipients when the following are true:
Exchange 2016 Cumulative Update 1 (CU1) is installed on the server.
Recipient validation is enabled on the server.
When an Edge Transport rejects a message because of this issue, the sender will receive a non-delivery report (NDR) with the status code 5.1.10, and the errorRecipient not found by SMTP address lookup. The recipient won’t receive the message.
From testing it appears that this bug impacts Edge Transport servers receiving email directly from the internet. Edge Transport servers that are used for hybrid mail flow with Exchange Online do not appear to be affected by this bug.
Microsoft’s advice to customers affected by this bug is to either:
Disable recipient validation on Exchange 2016 CU1 Edge Transport servers
Route inbound email to an Edge Transport server that has not been upgraded to Exchange 2016 CU1
Route inbound email directly to a Mailbox server
If you prefer not to bypass their Edge Transport server, and don’t have a non-CU1 Edge to route email to, then disabling recipient filtering on the Edge Transport server involves running the following command on the Edge Transport server:
You must be logged in to post a comment.