WDS to deploy Hyper-V Servers and VMs

I have several physical servers to deploy in the future.
The physical server will have Hyper-V and 3 pre-configured/syspreped VMs and of course the physical server will be "syspreped" too.
I´ts fine to deploy it using WDS?
It´s Ok, to deploy a sysprepd physical Hyper-V server via WDS?
It´s Ok, to deploy a sysprepd physical Hyper-V server with 3 syspreped VMs inside it?

Hi fborup,
Are you trying to run sysprep a server which installed Hyper-V role for new server installation? Microsoft does not support the use of Sysprep for a computer that has been
running in production for extended period of time and run sysprep then create a new image or clone from the computer. Sysprep is designed to prepare new installations of Windows for imaging.
After Server 2008 Hyper-v you can sysprep a Hyper-V server but Sysprep doesn’t supported for a virtual network on Hyper-V. We must delete any virtual networks before run the
Sysprep tool.
The related KB:
Sysprep Support for Server Roles
http://technet.microsoft.com/en-us/library/hh824835.aspx
Unsupported Sysprep scenarios
http://support.microsoft.com/kb/828287
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
For Virtual networks that are of the type "External Network", these will be resetted to "Internal Network", since sysprep "generalizes" anything related to hardware. This can easily be changed back once redeployed. Hence you really
don't need to delete any type of networks before running sysprep, and this goes for Server 2008, 2008R2, 2012 and 2012R2 (including 2012R2 with Update).

Similar Messages

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012
The following guide will enable you to:
1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager
! This should also work for Core installations of server 2012, but I haven't tried.
This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.
* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.
- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.
> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)
1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.
! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012
2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.
> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
> Next, is to get the MMC firewall snap-in working.
The reason for this, is to have a GUI available to configure it.
If you're happy without it, you may skip this and use a shell instead to do so.
? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)
! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level
# (In other words: allows the firewall to be remotely managed)
! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.
? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.
! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done
! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon,
# and choose run as admin on the bar below.
! Client: application MMC: select "file" --> Add/remove snap-in
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)
* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.
! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.
! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.
! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate
# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
# I recommend to choose yes; unless you like to pull some more hairs...
! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
! select yes
! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server
Done.
You can now manage your remote server through the familiar computer management GUI.
! Right-click your remote server, and select "Computer Management"
A few side notes:
? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.
If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.
Cheers!

As a little update to the post, I'd like to add that replication, clustering and migration will not work in workgroup environments. Unless someone can provide an additional guide for this, I'd recommend anyone to no even bother to try.
To manage the standalone hyper-v server in a remote location over the internet, I would recommend the following:
Install windows 8 pro (x86 uses less resources!) as a vm on the host, and assign 2 network connections to it.
1 external (shared with host) (be sure you have a dedicated ip-address for it!)
1 internal connection.
What I did was this:
As soon as you've installed the win8 guest, proceed with the guide as described.
For the 1st step of the guide (hosts-file) use the ip-address you will later assign to the "internal" network switch of the host!
In my example, I'm using 10.0.0.1 for the host, and 10.0.0.2 for the guest.
To be clear: I first used the guide on a LAN-environment, and did all the steps from a "real" client to server on the LAN.
Then, installed the win8 guest on the host using the "real" clients' hyper-v manager over the LAN.
Next, assigned the 2 network connections to the VM, and configured them as follows:
external - as you would to be able to make your guest reach the internet.
internal - I used the following config:
ip-address: 10.0.0.2
subnet: 255.255.255.252
gateway - blank
dns - Blank
Now, when you get to the console of the hyper-v server (host) or RDP to it, go to network settings.
You'll see that the internal card has been added here as well.
Configure it as follows:
ip-address: static - 10.0.0.1
subnet: 255.255.255.252
gateway - blank
dns - blank
You should now be able to ping your guest (win8) on 10.0.0.2 if it's running.
Don't forget to enable ping response (option 4 on the host) to test connectivity the other way around as well (guest to host)
When you're done, you'll be able to RDP to the guest OS over the internet, and then connect to the host with server manager, hyper-v manager, and MMC.
Don't forget to enable each module on the hosts' firewall to make the snap-ins work!
Remote volume management requires your guest/client firewall INcoming ports to be enabled as well! not just the host.
Either update the firewall rules from the MMC gui as described in the guide, or use the following commands on the
hosts' powershell:
Enable the firewall rules with the command Enable-NetFirewallRule -DisplayGroup "USE_THE_COMMANDS_BELOW" (include the " " in the command)
Remote Service Management
Remote Volume Management
Remote Event Log Management
Remote Scheduled Tasks Management
Windows Firewall Remote Management
Windows Remote Management
You can get the list with Get-NetFirewallRule -DisplayName *management*
You can get the list with Get-NetFirewallRule -DisplayName *remote*
Commands provided with credits to F. verstegen
Cheers,
Michael.
Sigh...

2 Hyper-V Servers with Failover Cluster and a single File Server and .VHDs stored on a SMB 3 Share

I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs) and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs). I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
all .VHDs stored on a SMB 3 Share on the File Server.
The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
\\fileserver\shareforVHDs
It is possible? How Cluster will understand the
\\fileserver\shareforVHDs as a cluster disk and offer HA on it?
Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
Storage Spaces makes difference in this case?
All based on wind2012 R2 STD English version

I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs) and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs). I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
all .VHDs stored on a SMB 3 Share on the File Server.
The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
\\fileserver\shareforVHDs
It is possible? How Cluster will understand the
\\fileserver\shareforVHDs as a cluster disk and offer HA on it?
Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
Storage Spaces makes difference in this case?
All based on wind2012 R2 STD English version
You can do what you want to do just fine. Hyper-V / Windows Server 2012 R2 can use SMB 3.0 share instead of a block storage (iSCSI/FC/etc). See:
Deploy Hyper-V over SMB
http://technet.microsoft.com/en-us/library/jj134187.aspx
There would be no shared disk and no CSV just SMB 3.0 folder both hypervisor hosts would have access to. Much simplier to use. See:
Hyper-V recommends SMB or CSV ?
http://social.technet.microsoft.com/Forums/en-US/d6e06d59-bef3-42ba-82f1-5043713b5552/hyperv-recommends-smb-or-csv-
You'll have however a limited solution as your single physical server being a file server would be a single point of failure.
You can use Storage Spaces just fine but you cannot use Clustered Storage Spaces as in this case you'll have to take away your SAS spindles from your R720 box and mount them into SAS JBOD (make sure it's certified). So you get rid of an active components
(CPU, RAM) and keep more robust all-passive SAS JBOD as your physical shared storage. Better then a single Windows-running server but for a true fault tolerance you'll have to have 3 SAS JBODs. Not exactly cheap :) See:
Deploy Clustered Storage Spaces
http://technet.microsoft.com/en-us/library/jj822937.aspx
Storage Spaces,
JBODs, and Failover Clustering – A Recipe for Cost-Effective, Highly Available Storage
http://blogs.technet.com/b/storageserver/archive/2013/10/19/storage-spaces-jbods-and-failover-clustering-a-recipe-for-cost-effective-highly-available-storage.aspx
Using
Storage Spaces for Storage Subsystem Performance
http://msdn.microsoft.com/en-us/library/windows/hardware/dn567634.aspx#enclosure
Storage
Spaces FAQ
https://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx
Alternative way would be using Virtual SAN similar to VMware VSAN in this case you can get rid of a physical shared storage @ all and use cheap high capacity SATA spindles (and SATA SSDs!) instead of an expensive SAS.
Hope this helped :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Is it possible to deploy SharePoint or its Service Applications on: multiple DB-Servers and multiple SQL Instances?

Hello Forum,
We have a SharePoint 2013 farm (Enterprise edition) that uses one single SQL Server 2012 (Standard edition). That statement means: All my SharePoint DBs e.g. (Config, Admin, Content, and Service Apps) DBs are hosted and running onto one single instance e.g.
Server1\SQLInstance1.
We have some new requirements to install and configure BI tools such as: PerformancePoint services and PowerPivot. BI tools require either SQL Server 2012 Enterprise or BI editions, and we do NOT want to upgrade our current SQL Server1\SQLInstance1
Instead, We have other separate SQL Server instance which is enterprise edition let's name it (ServerX\InstanceX) that is running standalone, and we are thinking or using it, and my 2 questions are:
1) Can we use this other separate
SQL Server instance which is enterprise edition to host the create and hosts the DBs of PerformancePoint services and PowerPivot ?
2) My second question is the same: Can I create PerformancePoint services application in my SharePoint farm, But in the Database Server field, I fill up
the details of the other DB server ServerX\InstanceX which is the one that is SQL
enterprise edition ? Will this work ?
Any official Microsoft resources/links tell that it is possible to deploy SharePoint or its service applications on multiple DB-Servers and multiple SQL Instances?

Thank you Alex and Anil,
What are the ramifications of that?
I mean, Assuming that I have created such a farm where most of SarePoint DBs in Standard SQL instance while the PerformancePoint service application and others e.g. PowerPivot and reporting service are deployed and configured onto other Enterprise SQL instance.
Are there any recommendations or concerns that you would like to draw my attention to ?

Can we recover SCCM 2012 R2 site Servers and SQL DB from hyper V or Vmware VM snapshot

Hi Folks
Can we recover SCCM 2012 R2 site Servers and SQL DB from hyper V or Vmware VM snapshot
if yes is there any challenges or any document available from Microsoft on Hyper V SCCM VM snapshot recovery.

I've made it work and it "should" work. However it's not the best practice method of site recovery. You should recover using a SQL restore.
See good example
http://anoopcnair.com/2012/07/01/sccm-configmgr-2012-primary-site-server-and-database-recovery-part-1/
Note that you should be using snapshots only on occasions when you are carrying out a risky operation. You can revert it the operation fails. It is not a substitute for a robust backup solution.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

RDS 2012 - using Virtulization Host role on HyperV Servers hosting VMs

I have an existing RDS2012 farm which is working great with Session Hosted Desktops.
I'm looking to evaluate pooled Windows 8.1 desktops and know I need to run these on HyperV servers with the RDS Virtualization host role installed.
I have an existing production HyperV cluster for servers and am wondering if i should use this for the Windows 8.1 VMs and if so, do i need to install the virtualization host role on all servers in this cluster.
Or would it be best practise to dedicate a HyperV server/cluster purely for hosting the RDS Win8 client VM's (and keeping the virtualization host role off the production HyperV cluster)?
Thanks.

Virtual Desktops have different performance and capacity requirements than typical server workloads. It is recommended to visualize desktops on hyper-visors dedicated to desktops only. For capacity planning for virtual desktops on Hyper V, refer
to this document -> http://download.microsoft.com/download/2/4/B/24B5EC7D-1D03-49A2-B792-C7EDF24549EE/Windows_Server_2012_Capacity_Planning_for_VDI_White_Paper.pdf
HTH,
JB

Windows Server 2012 Standard License and VMs

Hi,
With one Window server 2012 Standard activated license, I will get 2 VMs. So is there a limit with Windows Server 2012 standard license I can stack and the the number of VMs I can create on one server or across servers (virtual environment). Consider that
all Windows server 2012 standard licenses are activated. If there is no limit on VM creation by add Standard license then why did Microsoft come with Data center licenses with unlimited VMs.
How does the standard license work on Vmware environment. Is there a limit on the number for VMs that we can create.
Please advise me.
Thanks.

If i had one server 2012 standard with its key, i could run it as a vm but not as a virtual host without having the license right?
a single WS2012STD license, allows you to run a server machine (hardware), if that hardware has no more than 2 processors. In this case, you can run 2 VMs, each VM is running WS2012STD. You can also run WS2012STD as the host hypervisor via Hyper-V.
So, that's really 3 OS installations, on the same 2proc machine. The limitation is that the host hypervisor OS is only permitted to do Hyper-V stuff, it's not permitted to use that OS for anything other than hypervisor functions.
If you implement in this way, you would only have purchased a single license for WS2012STD, so you would only have a single key, so you would use that key for the 3 OS installations.
If i bought the single server 2012 standard license, i'd be able to install it as a Host and activate with the key and it'd give me rights to run 2vms on it and for those vms i would have to have 2 keys to activate after installing server 2012 standart
software on them right?
see above.
if you buy via Volume Licensing, things change a little bit due to MAK/KMS keys (it gets a whole lot simpler :)
Sorry for being unclear on the clusters part, i meant HA/failover. we have 2 2008R2 enterprise servers in cluster with shared storage and i was trying to clarify how could i add more vms there.
assuming your failover solution involves traditional server hardware, each failover node is just another hardware machine, so, for each node you have to count up the procs and VMs, just as you would do for non-failover implementations.
if a server is installed and running/executing, it needs to be licensed.
with current configuration, each server is hosting 2vms and if anything happens single host can accommodate all four. I am assuming we have 2 enterprise licenses for them, but if i wanted to run 4vms on each host, we have to buy 2 more enterprise licenses
and install vm togerther with their keys?
There is no Enterprise for WS2012? (WS2012 has STD and DCE)
do you mean as in WS2008R2ENT ?
You can re-assign licenses from one machine to another machine (under the Volume Licensing terms. I'm not sure about Retail terms, you should check that). There are limitations on how often you can reassign licenses (no more than every 90days)
If hardware "fails", you are allowed to reassign the license in a shorter period than 90days.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Cannot deploy VM from VMM and AppController

Hi All,
I have been installing the VMM and AppController. Initially all went well.
After I install RU5 there occurs a problem where I can not deploy vm of VMM and AppController with error messages like that :
host A kuilab01
on kuilab01 still available memory of 11GB
host B krslab03
Thank's
Best Regards

Hello,
Did you try to reboot your host?
Did you update the agent of each Hyper-V after the UR5?
Go to the fabric tab to see if the status of each Hyper-V is OK.

Hyper V Lab and Live Migration

Hi Guys,
I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
The problem I have is my shared storage is a bit of a cheat as I have one disk assigned in each host and each host has starwinds virtual SAN installed. The hostA has an iscsi connection to hostB storage and visa versa.
The issue this causes is when the hosts shutdown (because this is a lab its only on when required), the cluster is in a mess when it starts up eg VMs missing etc. I can recover from it but it takes time. I tinkered with the HA settings and the VM settings
so they restarted/ didnt restart etc but with no success.
My question is can I use something like SMB3 shared storage on one of the hosts to perform live migrations but without a full on cluster? I know I can do Shared Nothing Live Migrations but this takes time.
Any ideas on a better solution (rather than actually buying proper shared storage ;-) ) Or if shared storage is the only option to do this cleanly, what would people recommend bearing in mind I have SSDs in the hyper V hosts.
Hope all that makes sense

Hi Sir,
>>I have 2 Hyper V hosts I am setting up in a lab environment. Initially, I successfully setup a 2 node cluster with CSVs which allowed me to do Live Migrations.
As you mentioned , you have 2 hyper-v host and use starwind to provide ISCSI target (this is same as my first lab environment ) , then I realized that I need one or more host to simulate more production scenario .
But ,if you have more physical computers you may try other's progects .
Also please refer to this thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e9f81a9e-0d50-4bca-a24d-608a4cce20e8/2012-r2-hyperv-cluster-smb-30-sofs-share-permissions-issues?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Server 2012 R2 Hyper-v Servers not being discovered by the mp

Sorry if this is a dup question. I did see the one for 2008 but that didn't fix my issue.
I have 4 hyper-v servers running server 2012 r2 in a cluster. I have scom 2012 r2 and it detects the cluster and 3 out of the 4 hyper-v servers. the 4th server it can see under windows but does not discover the hyper-v components.
Any assistance would be appreciated.

Hi,
You can install the Agent on the server manually to check the result.
http://technet.microsoft.com/en-us/library/hh212853.aspx
Niki Han
TechNet Community Support

Using Datasources.xml in backup of Hyper-V cluster and standalone Hyper-V hosts

Hi!
I have a DPM 2012 server which I have used to backup standalone Hyper-V hosts and Exchange 2010 server active DAG node. Since yesterday I have added Hyper-V cluster backup, and now I have generated Datasources.xml using .\DSConfig.ps1 on one of the
Hyper-V nodes.
My question is: Do I have to manually add other protected data sources (Exchange, VMs from standalone hosts) to Datasources.xml? Or this xml is used only for CSV clusters?
Thanks in advance for your answers!
Kruno

Hi,
Yes, but the key is wrong - this is required as part of the csv serialization configuration.
On the DPM Server, Copy / paste below into notepad, then save as MaxAllowedParallelBackups.reg on the DPM server, then right-click and select merge.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\2.0\Configuration\MaxAllowedParallelBackups]
"Microsoft Hyper-V"=dword:00000001
Please review these two sources to assist you.
http://social.technet.microsoft.com/wiki/contents/articles/17493.protecting-hyper-v-virtual-machines-with-system-center-dpm-2012.aspx
http://blogs.technet.com/b/dpm/archive/2010/12/09/system-center-data-protection-manager-2010-hyper-v-protection-configuring-cluster-networks-for-csv-redirected-access.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Non Domain Servers and Workstations

Hi,
we are trying to deploy SCCM 2012 clients to non domain servers, and we are also in the process of trying to find out what the best way we can clean up machines from sccm that have not logged in 90days or more.
From my understanding if I turn on only discover machines that have logged on to the domain in a given period of time than that means if a server has not logged in will not be discovered which can be an issue when patching, and also what do I need to do
with the non domain servers with sccm client installed on the servers.
can you please help me with this that would be greatly appreciated
Thanks Tom

Hi,
This blog post does a good job explaining the steps to manage non-domain machines with ConfigMgr 2012:
http://blogs.technet.com/b/anilm/archive/2012/05/06/managing-workgroup-clients-in-configuration-manager-2012.aspx
This technet article also has more detailed information about client communication for workgroup computers:
http://technet.microsoft.com/en-us/library/gg712701.aspx#Plan_Com_X_Forest
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Need recommendation - iis with two physical servers and clusters

Hello,
I was hoping to get a recommendation/opinion or two on the configuration I've inherited. I'm looking
at the following configuration using weblogic 8.1 sp4 server (to be upgraded to sp6) running on two physical machines:
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7001
ManagedServer2:7010
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:7001
ManagedServer4:7010
On MachineA: IIS Proxy Plugin with parameter in .ini file
WeblogicCluster: MachineA:7001, MachineA:7010, MachineB:7001,MachineB7010
Naturally, the IIS is acting as a round robin load balancer..
The domains were created using the wizard on both machines and basic domain template..
For proper failover to be taken advantage of, does something different need to be configured? Or is it fine?
And if so, does group replication have something to do with it?
Should either of the clusters be Managed Servers across physical machines?
or should this just be one cluster of 4 managed servers across two machines?
I really am not sure on any of this, even though i've read through much of the documentation for clustering..twice.
I should mention that there is only a .war file deployed with 4 connection pools and 4 Data Sources..No EJBs or JMS
Would really appreciate any feedback or opinions/advice..
Thanks

This is what I'd do
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7010
ManagedServer2:7020
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:8010
ManagedServer4:8020
I just changed the port numbers so they flow and have a pattern - 70* port numbers belong to cluster 1, 80* port numbers belong to cluster 2. No technical benefit apart from it makes it tidier in my opinion.
Port 9001 for the admin server is normally the domain wide admin port - you could be using that, so that's fine, but my admin server is running 7001.
You also only need one admin server per domain, this can run on MachineA
Replication groups are used to help WLS figure out where to place the secondary http session. It will try servers on a different machine/replication group first, if none available, it will create secondary on the same machine.
What you will end up with is a domain with 4 managed servers in it. The admin server will run on machineA, say using port 7001, each of the managed servers will contact the admin server to download it's config.
The cluster1 will contain 2 managed servers and the same for cluster2.
providing you have your cluster multicast addresses set up and the cluster is working, that should be all you need to do for the session failover.
There's some BEA sample code somewhere which will deploy a web-app and show which managed server you've attached to. If you find that and then connect through IIS, shut down the server that the JSP tells you, you should be able to see the session fail-over nicely.
Hope that helps,
Pete

Problem with WMI after using MDT/WDS to deploy

Hi
I am using MDT with WDS to deploy windows server.
All is fine, besides WMI from Zenoss for monitoring, it show's me errors like
" Could not read the Windows event log (NT_STATUS_ACCESS_DENIED). Check your username/password settings and verify network
connectivity."
If i do the same installation by hand, everything works.
Do you have any idea how installation from MDT differs from by hand installation, that could have impact on WMI?

Hi Bartosz Kupiecki,
May you must have some misunderstand of WDS and MDT deploy, your issue may occur because your MDT has some unattended file or customize the install image (has setting
some special configuration which different with the your manually installed system), please remove this customize configuration then try again.
More information:
MDT 2013 – Part I: MDT Configuration; Capture a Windows Server 2012 R2 Base OS Image
http://blogs.technet.com/b/askpfeplat/archive/2014/08/04/mdt-2013-part-i-mdt-configuration-capture-a-windows-server-2012-r2-base-os-image.aspx
There have a specific forum to support the MDT question, more detail about the MDT question please post to the MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Current version of integration services on Hyper V host and ugrading versions on VM's

Greetings!
I am looking for where the latest version number of integration services is posted, so I may verify what it should be. I am able to query using powershell the vm's on the hosts and get a return of the current version installed. However, I seem to be
unable to find out the current version of IS on the hosts themselves. How do I get this information?

With all current releases of Hyper-V:
When you patch your Hyper-V Server and reboot, the vmguest.iso is generated dynamically to match the release of the Hyper-V Server.
This is historic and was designed to ensure compatibility of the ICs in the VM with the Services of the host.
That said, only Hyper-V 2012 R2 can give you the 'latest' integration components, but they might not function well if VMs are moved to older versions of Hyper-V. That is why 2012 R2 in a VM is 'not supported' on Hyper-V 2008 R2 or 2008 (for example).
In the future Integration Components will be through Windows Update (if your Hyper-V Server is 'Windows 10" or later):
http://blogs.technet.com/b/virtualization/archive/2014/11/11/hyper-v-integration-components-are-available-through-windows-update.aspx
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

WDS to deploy Hyper-V Servers and VMs

Similar Messages

Maybe you are looking for