Extending a Partition on Server 2012

I am looking to extend my E partition with the 68GB of unallocated space. The extend volume option is greyed out and I am unsure how to modify the sizes.
I am running Server 2012 R2 with RAID 1.
This topic first appeared in the Spiceworks Community

Similar Messages

Error: Invalid Parameter when trying to extend volume in Windows Server 2012

From VMware, I added space to a Hard Drive to a Windows Server 2012 VM. I then went into the WinServer console, and opened Disk Management. I did a rescan on the disk. It found the extra space. I right mouse click on the Disk,
and choose Extend Volume, choose the available space, and then an error returned of 'Invalid Parameter'.
In Disk Manager, the new larger space is assigned, but Windows Explorer and everything else only recognizes the original smaller size.
EventManager shows Event ID 265: A pointer device did not report a valid unit of angular measurement. Event ID 257: A pointer device reported a bad angular physical range. Event ID 258: A pointer device reported a bad angular logical range.
Anyone have a solution for this problem?

Hi,
Please try to use the command line utility diskpart to extend the drive.
1. Open a command prompt
2. Type in diskpart
3. Type list volume
4. Type select volume #
5. Type extend [size=n] [disk=n]
For more detailed information about diskpart, please see:
DiskPart Command-Line Options
http://technet.microsoft.com/en-us/library/cc766465(v=ws.10).aspx
You could refer to the article below to troubleshoot the issue:
Windows Server 2008 drive doesn’t expand correctly after extending in VMware VI client
http://consultingblogs.emc.com/greggrobertson/archive/2010/05/27/windows-server-2008-drive-doesn-t-expand-correctly-after-extending-in-vmware-vi-client.aspx
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
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.

Adding second domain controller in Windows server 2012 R2

Hello, our primary domain controller is currently on a machine that has Windows Server 2008 R2 Standard. We are planning to setup a second domain controller as a failover to our primary domain controller. My question is, can we have a secondary domain
controller on a Windows Server 2012 R2 even if our primary domain controller is on a machine that has Windows Server 2008 R2?

I think I found the answer to my question.
http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx
"In Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep
/forestprep and adprep /domainprep automatically run and report the results of the operations.
Some organizations may prefer to run Adprep.exe separately in advance of an AD DS installation. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
In Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. The computer where you run it can be either
domain-joined or in a workgroup.
The version of Adprep.exe in Windows Server 2012 includes new syntax and parameter options in order to run it remotely. For more information, see
Adprep."
For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012, see
Windows Server 2012: Changes to Adprep.exe.

Boot up of Windows Server 2012 Essentials seems slow (extended Please Wait screen) and there are errors in Health Report

Dear Sir or Madam,
I have been experimenting with the evaluation version of WS2012e trying to get the installation and subsequent build into an optimal set up, and once I have everything I want it to do mapped out, I'll set it up with the full version with using the key that
I bought.
However, I've noticed that the server seems to experience a delay during cold boot - it sits with a Please Wait screen for about 60-90 seconds before it presents the screen with an option to Log on. I have also discovered from running Health
Report, that there are some entries in the event logs which appear to coincide with start up times, and which seem to be interconnected to each other in the issues they are describing, and I have copied an example of one of those health reports below.
I assume that everything sorts itself out in due course, because the events say the process will be re-attempted and these errors don't repeat again after the system has booted up. I also have the server set to suspend when not in use with the Lights
Out add in, so it shouldn't need to cold boot often - but I wondered if there's a way to correct these errors so that they don't hold up the boot up process? I'm also concerned that these errors will cause me later problems with storage pools and
the like at a later date - the disk replication one seems particularly worrying. Alternatively, are these errors just a normal part of the start up process - the timing of when different processes start relative to each other - and can be safely ignored?
In trying to understand what the events describe, I thought that WE2012e acted as its own Domain Controller, and yet it seems from the event log entries that it is waiting for another server to respond to AD / DC requests (but there isn't another server
on my home network). The other thing I remember from when I first tried out WS2012e, is that it took control of DHCP or DNS from the router, and I found that frustrating when waking up my laptop and it wouldn't connect to the internet until the server
had fully booted up and re-asserted its network settings. Is this another symptom of the same problem? I remember seeing a posting at the SBS Diva's site about how to update the server so that it gave connected PCs a backup option for connecting
to the internet when the server wasn't available, and was going to try to find that again to see if that helped.
By way of background - there isn't another server in my home network. This is an attempt to do a clean install onto the same hardware that I ran the initial trial of WS2012e, now that the trial has expired, so I'm not trying to migrate from an existing
server. I moved all the data on the trial server off onto an external disk, with the intention of importing it back once I had the Storage Pools set up the way I wanted on the new build, and since I didn't want to keep anything else about the server
trial. Am I correct in thinking that I don't need to go down the Migration route during installation, and can go through a Clean install in this circumstance?
I'm running on an Asus P8-H77-i motherboard, with an i5-3470s CPU and 16MB RAM, and I have WS2012e installed on 256Mb SSD formatted under GPT with uEFI boot - the latter being the main reason for the reinstall, instead of just giving the Evaluation
version the new key on the original MBR set up. I've also enabled Intel Rapid Storage and Rapid Start - and successfully set aside the hibernate partition on the SSD - but discovered that this is about forcing a hibernate after suspend, allowing
the system to power down until its needed again, and then resuming from hibernate on the SSD rather than cold boot each time. That seems to work, but doesn't improve the cold boot times at all, which was what I was hoping for - ideally the way my
laptop will boot from cold in a few seconds into Windows 8.
Yours faithfully,
Avon
======
Health Report extract.
Critical Errors in Event Logs in Last 24 Hours
DFSR
Event ID: 3221226674
The DFS Replication service failed to contact domain controller to access
configuration information. Replication is stopped. The service will try again
during the next configuration polling cycle, which will occur in 60 minutes.
This event can be caused by TCP/IP connectivity, firewall, Active Directory
Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)
Last occurrence: 26 May 2014 18:51:28
Total occurrence(s): 2
DNS
Event ID: 2147487661
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS
data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet
Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
Last occurrence: 26 May 2014 18:51:15
Total occurrence(s): 2
ADWS
Event ID: 3221226674
This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically.
Last occurrence: 26 May 2014 18:51:08
Total occurrence(s): 2
NTDS General
Event ID: 2147486534
The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,
Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification) and LDAP simple binds that
are performed on a cleartext (non-SSL/TLS-encrypted) connection. Even if no clients are using such binds,
configuring the server to reject them will improve the security of this server.
Some clients may currently be relying on unsigned SASL binds or LDAP simple binds over a non-SSL/TLS connection,
and will stop working if this configuration change is made. To assist in identifying these clients, if such binds occur this
directory server will log a summary event once every 24 hours indicating how many such binds
occurred. You are encouraged to configure those clients to not use such binds. Once no such events are observed
for an extended period, it is recommended that you configure the server to reject such binds.
For more details and information on how to make this configuration change to the server, please see http://go.microsoft.com/fwlink/?LinkID=87923.
You can enable additional logging to log an event each time a client makes such a bind, including
information on which client made the bind. To do so, please raise the setting for the "LDAP Interface Events" event logging category
to level 2 or higher.
Last occurrence: 26 May 2014 18:51:00
Total occurrence(s): 2
=======

Hi KerguelanAvon,
Based on your description, it seems to be hard to narrow down the cause of this issue. Please refer to following operations and monitor the result. It may help us to go further, and then solve this issue.
1. Please refer to the following article and troubleshoot slow boot.
New Slow Logon, Slow Boot Troubleshooting Content
2. On your server 2012 essentials, please start a BPA scan and fix all that it can find, then monitor the result.
Regarding to those critical Errors in Health Report, please perform
Dcdiag on the server. Meanwhile, please refer to the following article and troubleshoot network connectivity, firewall setting and AD DS issue.
DFSR Event 1202 (DFS Replication)
Hope this helps.
Best regards,
Justin Gu
Hi Justin,
I'm reading through the links you referred me to but it's taking a while. In the meantime I tried running BPA as you suggested. I'm sure when I ran it before, it didn't say much beyond 81 checks completed, and I couldn't find a way to get any
more detail.
Now it says
Problem:
The DNS client is not configured to point only to the internal IP address of the server.
Impact:
If the DNS client is not configured to point only to the internal IP address of the server, DNS name resolution can fail.
Resolution:
To resolve this problem:
1. From the client computer, open the Properties page for the network connection.
2. Make sure that DNS is configured to point only to the internal IP address of the server.
Except that it is.
Connection-specific DNS Suffix:
Description: Broadcom 802.11n Network Adapter
Physical Address: ‎00-1B-B1-28-AE-63
DHCP Enabled: Yes
IPv4 Address: 192.168.1.133
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: 03 June 2014 21:56:49
Lease Expires: 05 June 2014 20:24:20
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.49
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::80ef:48d5:9fde:f10e%14
IPv6 Default Gateway:
IPv6 DNS Server:
I'll try rebooting from the current windows 7 build over to windows 8 on my dual boot laptop, to see if that makes any difference, since it is the only other client PC connected to the server at the moment.
Thanks, Avon.

Task Sequence Windows Server 2012 format and partition issue when using MDT2012

Hi all,
Currently I'm working on a task sequence to deploy a Windows Server 2012 image. We've integrated MDT2012 Update 1 in SCCM2012 SP1 and created a default 'Server Task Sequence'. This task sequence deploys the install.wim to a server which has multiple disks
attached.
We've configured multiple format and partition disk steps to create the following partition layout:
Disk 0: 499MB BDEDrive (do not assign drive letter) + 40GB OSDisk
Disk 1: 40GB Programs
Disk 2: 40GB Data
Disk 3: 25GB User
When the task sequence is finished I've noticed the drive letters assigned to the disk are not correct. In some cases the BDEdrive gets drive letter D assigned, sometimes drive letters are assigned starting with E, thus skipping drive
letter D.
The smsts.log files show an error when it's re-assigning drive letters after booting into Windows. Looks like an error in the DiskPartScript.txt.
<![LOG[==============================[ OSDSetupHook.exe ]==============================]LOG]!><time="16:59:40.889-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="osdsetuphook.cpp:186">
<![LOG[Executing task sequence]LOG]!><time="16:59:40.905-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="osdsetuphook.cpp:279">
<![LOG[Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".]LOG]!><time="16:59:40.920-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="basesetuphook.cpp:366">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="environmentscope.cpp:659">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="16:59:40.936-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776"
file="environmentscope.cpp:659">
<![LOG[Debug shell is enabled]LOG]!><time="16:59:43.806-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1440">
<![LOG[Successfully enabled debug command shell support.]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="debugwindow.cpp:156">
<![LOG[Configuring local administrator account]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="basesetuphook.cpp:1462">
<![LOG[Re-assign all drive letters...]LOG]!><time="16:59:43.884-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="diskutils.cpp:1941">
<![LOG[Executing command line: "C:\WINDOWS\system32\diskpart.exe" /s "C:\WINDOWS\TEMP\DiskPartScript.txt"]LOG]!><time="16:59:43.900-120" date="05-10-2013" component="OSDSetupHook" context=""
type="1" thread="776" file="commandline.cpp:827">
<![LOG[Process completed with exit code 2147942487]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="1" thread="776" file="commandline.cpp:1123">
<![LOG[Diskpart.exe STDOUT:
Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: SRV03
Volume 1 is the selected volume.
DiskPart successfully removed the drive letter or mount point.
The volume you selected is not valid or does not exist.
There is no volume selected.
]LOG]!><time="16:59:50.249-120" date="05-10-2013" component="OSDSetupHook" context="" type="3" thread="776" file="diskutils.cpp:1807">
When I take a look at the generated diskpart_script.log file the volume D gets selected twice, which fails the second time because of the first remove drive letter command.
This is the output in the diskpart_script.log file:
select volume D
remove letter=D
select volume D
remove letter=D
select volume E
remove letter=E
select volume F
remove letter=F
select volume H
remove letter=H
select disk 0
select partition 1
assign
select disk 1
select partition 1
assign
select disk 2
select partition 1
assign
select disk 3
select partition 1
assign
It seems this error is caused by the first 'Format and Partition Disk' step before the 'Use Toolkit Package' step which is part of the default Server Task sequence. When I disable this Format and Partition step and create the partition manually
all looks ok showing no errors in the smsts.log file.
I've solved this by replacing the first 'Format and Partition Disk' step by an Powershell command which formats and partitions the disk.
Anyone seen this behavior?

I have a similar problem when I install windows on some clients. Have you found any explanation for the behavior?

Access 2007 ADP to SQL Server 2012 with extended protection

Hello,
I have a Access 2007 ADP client connecting to an sql server 2012. This works fine with standard security configuration, but when I activate extended protection on the SQL server, the Access client cannot connect to the server. I am using integrated security
with a domain user and get the error message
"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication."
In sql server logfile I find:
"SSPI handshake failed with error code 0x80090346, state 46 while establishing a connection with integrated security; the connection has been closed. Reason: The Channel Bindings from this client are missing or do not match the established Transport
Layer Security (TLS) Channel".
Is there any "easy" solution other than developing a new client based on an up to date Office version or Dot.Net?
Regards,
charles-f

Well, I have no problem connecting to the sql server from my pc using ssms with my domain account. I have also sucessfully create a odbc connection using the "SQL Server Native Client 11.0" driver and my domain account. My account is in a trusted
domain, so this seems not to be the problem.
To me it rather looks like if Access is using an old driver which does not support the tls encryption required by the extended protection settings.
regards, charles-f

Windows Server 2012 OS Partition Size recommendations

i might be wrong but i have always tried to keep the size of the OS partition to match a common physical HDD size ie 125GB, taking into consideration the Windows update patches and apps versions update.

Greetings. This is my first post, so please be kind.
The Storage Admin at my new job has defined Windows Server 2012 installs to have a 40 GB OS Partition. To me, this seems extraordinarily small. I know MIcrosoft's minimum is 32 GB.
Most of the servers I will be deploying will not have the applications on the OS partition, but I believe the page file will be on the OS partition.
Since most of these servers will also have 8 GB or more of RAM, what would be a good recommended size for the OS Partition?
Also, if someone could link me to articles written by technology leaders talking about this issue, I would appreciate it.
This topic first appeared in the Spiceworks Community

Evaluation of SQL Server 2012 R2 expired is there any way to extended the evaluation time?

Hello,
My Evaluation of SQL Server 2012 R2 expired is there any way to extended the evaluation time?
Please let me know,
Thank You! and Happy New Year

Hello,
Try to roll back the time of the computer to a few days back until you are able to perform an edition upgrade.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Windows Server 2012 Essentails - Can I get an extended trial for 10 days or so (really need this)

Greetings all, I'm currently running a trial version of Windows Server 2012 Essentials, and am very happy with this so moved all pcs and laptops over, reason in doing so was going to go to the full version from this trial, but then I thought about trialing
out 2012 R2 Essentials and have been running this with no issues and would rather spend the money on buying this version.
I have 2 days left of the trial license for 2012 Essentials, is there anyway I can extend this for an extra 10 days or so to give me enough time to finish of building the other server ?
Thanks..

Thank you Klockwork, well that's not very helpful of Microsoft :-(
Not sure why though they did allow you to extend with Server 2008..
Anyway I'll
find away.
Thanks
Again.

Disappearing disk space Windows Server 2012 R2 with SharePoint Server 2013 Enterprise

I've got an interesting problem with a virtual machine in our VMWare environment. It is Windows Server 2012 R2 with SharePoint Server 2013 Enterprise installed. I started out with a 60GB disk and it started running out of space, so I increased
it in VMWare and extended the partition to 100GB. Well, that lasted for a bit and so I extended it again. I've done this 3 or 4 times and now I've got a 160GB disk with about 2-3GB of space remaining (and it started with 10GB remaining).
WinDirStat shows 105GB of <Unknown> space being used, which is probably my issue. However, I can't determine what this is and it keeps growing like a tapeworm. The context menu on the <Unknown> files has all the options disabled,
so WinDirStat doesn't appear to have access to whatever the file(s) is/are. I've performed several chkdsk /f on the C: drive and nothing bad is reported. I don't have any restore points and am not running VSS (that I'm aware of). The pagefile
reports as being about 4.9GB, so that's not the issue. No large files are shown anywhere and my explorer settings are set to show me all files, including system files.
When I try to run WinDirStat with elevated permissions, it hangs and becomes unresponsive.
I've even resorted to running CCleaner to see if it found anything, but it simply found the standard temp files and such...about 1GB.
I'm pulling my hair out...and I don't have much to start with. Anyone have any ideas?
Thanks
Russ

It appears that somehow, Microsoft Fusion Assembly binding logging was turned on and many of the temp folders located at c:\users\username\AppData\Local\Microsoft\Windows\InetCache\IE were filling up with hundreds of thousands of Fusion HTM log files.
This is controlled by an entry in the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion\ForceLog which was set to 1. Hopefully, setting it back to zero will fix the issue. As a result of figuring this out, I have recovered almost 80GB of disk
space occupied by the log files.
I thought WinDirStat would show me what I needed to know, but it turns out TreeSize (which I've used in the past) works much better.
Russ

0x8056530b error enabling disk deduplication on Windows Server 2012 R2 Volume - any ideas why or how to fix?

I'm getting the following error when trying to enable disk de-duplication on a volume on my Windows 2012 R2 file server. The error is:
"There was an error updating Data Deduplication on volume: MSFT_DedupVolume.Volume='\\?\Volume{8dfc4322-9997-11e3-93f5-005056a84b9b}\' - HRESULT 0x8056530b, The specified volume type is not supported. Deduplication is supported on fixed, write-enabled
NTFS data volumes and CSV backed by NTFS data volumes."
The volume in question is a 1TB VMFS volume mounted to the virtual machine that is the Windows file server. I could find no info anywhere that references this error as it relates to a standard mounted volume or VMware or VMFS.
Any ideas on what could be the problem or how to fix it? I could find nothing in the log files other than an entry which is basically a repeat of the error above.
Any help would be greatly appreciated.
- ADEHART
P.S. This is a volume that was previously mounted on an older Windows 2003 server. Not sure if that may make a difference.

have you compared this issue to the ones that are successful and compared what is different?
Have you made sure of the following:
Servers
See the following list for server requirements for deduplication:
• Server hardware should meet the minimum requirements for running Windows Server 2012. The deduplication feature was designed to support minimal configurations such as a single processor system with 4 GB of RAM and one SATA hard disk drive.
• If you plan to support deduplication on multiple volumes on the same server, you need to plan an appropriately size for the system to ensure that it can process the data. The general rule is that the server needs 1 CPU-core and 350 MB of free memory to run a deduplication job on a single volume, and that job can process about 100 GB per hour or around 2 TB per day. Deduplication scales with additional CPU core processors and available memory to enable parallel processing of multiple volumes.
For example: If you have a server with 16 CPU core processors and 16 GB of memory, deduplication uses 25% of the system memory in the default Background Processing mode, and in this case, that would be 4 GB. If you divide by 350 MB, you can calculate that the server could process about 11 volumes at a time. If you add 8 GB of memory, the system could process 17 volumes at a time. If you set an optimization job to run in Throughput mode, the system will use up to 50% of the system’s memory for the optimization job.
• Data Deduplication supports up to 90 volumes at a time; however, deduplication can simultaneously process one volume per physical CPU core processor plus one. Hyper-threading does not impact this because only physical core processors can be used to process a volume. A system with 16 CPU core processors and 90 volumes will process 17 volumes at a time until all 90 volumes are done, if there is sufficient memory.
• Virtual server instances should follow the same guidance as physical hardware regarding server resources.
Volumes
Volumes that are candidates for deduplication must conform to the following requirements:
• Must not be a system or boot volume. Deduplication is not supported on operating system volumes.
• Can be partitioned as a master boot record (MBR) or a GUID Partition Table (GPT), and must be formatted using the NTFS file system.
• Can reside on shared storage, such as storage that uses a Fibre Channel or an SAS array, or when an iSCSI SAN and Windows Failover Clustering is fully supported.
• Do not rely on Cluster Shared Volumes (CSVs). You can access data if a deduplication-enabled volume is converted to a CSV, but you cannot continue to process files for deduplication.
• Do not rely on the Microsoft Resilient File System (ReFS).
• Can’t be larger than 64 TB in size.
• Must be exposed to the operating system as non-removable drives. Remotely-mapped drives are not supported.
Note
Files with extended attributes, encrypted files, files smaller than 32 KB, and reparse point files are not processed by deduplication.

Failure to create a shared protection point during Windows Server 2012 R2 backup.

Several partitions on a system disk have been extended as well as the backup destination partition. After that Windows Server 2012 R2 failed the backup of a system disk with the following error message 0x8004230C. The Server stated it had failed to create
a shared protection point on source volumes and indicated a problem with volume shadow writer. What needs to be done to fix this error and does it have anything to do with partitions being extended?
Vladimir Shipitsyn

Hi,
What destination did you use to do the previous unsuccessful backup? You could try the steps in the article below to troubleshoot errors where the cause is reported by an underlying layer to Windows Server Backup.
Diagnosing Failures in Windows Server Backup - Part 1 (VSS/SPP Errors)
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
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.

ASA and RADUIS on Windows server 2012

hi i have ASA5505 i want to get the Authentication from Raduis Server using NPS on windows Server 2012 i test the Raduis Server over "Kerio Control VMware Virtual Appliance" its work Perfect for testing my Setting on Raduis but with the ASA5505 i get this message "Error authentication rejected aaa failure"
Running Config
: Saved
ASA Version 9.1(3)
hostname NazcoFW
domain-name default.domain.invalid
enable password XgEKS9WizHnI9IUJ encrypted
xlate per-session deny tcp any4 any4
xlate per-session deny tcp any4 any6
xlate per-session deny tcp any6 any4
xlate per-session deny tcp any6 any6
xlate per-session deny udp any4 any4 eq domain
xlate per-session deny udp any4 any6 eq domain
xlate per-session deny udp any6 any4 eq domain
xlate per-session deny udp any6 any6 eq domain
passwd XgEKS9WizHnI9IUJ encrypted
names
interface Ethernet0/0
switchport access vlan 22
interface Ethernet0/1
interface Ethernet0/2
switchport access vlan 12
interface Ethernet0/3
interface Ethernet0/4
shutdown
interface Ethernet0/5
shutdown
interface Ethernet0/6
shutdown
interface Ethernet0/7
switchport access vlan 32
shutdown
interface Vlan1
nameif NAZCO
security-level 100
ddns update hostname OSI
dhcp client update dns server both
ip address 172.16.200.1 255.255.255.0
interface Vlan12
nameif outside4
security-level 0
ip address 172.16.4.254 255.255.255.0
interface Vlan22
nameif Outside20
security-level 0
ip address 172.16.20.254 255.255.255.0
boot system disk0:/asa913-k8.bin
ftp mode passive
dns domain-lookup NAZCO
dns server-group DefaultDNS
name-server 10.1.1.1
name-server 10.1.2.1
domain-name default.domain.invalid
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object network HP5220
host 10.10.10.105
object network ak20
host 10.10.10.110
object network hp5520
host 192.168.2.105
object network HP7000
host 192.168.2.106
object network HP5520
host 192.168.2.105
object network ak04
host 10.10.10.110
object network HP400
host 192.168.2.107
object network out04
range 192.168.2.200 192.168.2.220
object network AK04
host 10.10.10.110
object network oooo
subnet 10.10.10.0 255.255.255.0
object network 444
host 10.10.10.110
object network OSITOINT
subnet 10.10.10.0 255.255.255.0
object-group network OSItoOUT04
network-object object out04
access-list outside20_access_in extended permit icmp any4 any4
pager lines 24
logging enable
logging asdm-buffer-size 512
logging trap informational
logging asdm informational
logging host NAZCO 10.10.10.10 17/6161
logging debug-trace
logging permit-hostdown
mtu NAZCO 1500
mtu Outside20 1500
mtu outside4 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-721.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (NAZCO,outside4) source dynamic any interface dns
nat (NAZCO,Outside20) source dynamic any interface dns
route Outside20 0.0.0.0 0.0.0.0 172.16.20.1 1
route outside4 0.0.0.0 0.0.0.0 172.16.4.1 11
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
aaa-server Keefa-Raduis protocol radius
aaa-server Keefa-Raduis (NAZCO) host 172.16.200.10
key *****
radius-common-pw *****
user-identity default-domain LOCAL
aaa authentication enable console LOCAL
aaa authentication http console LOCAL
aaa authentication serial console LOCAL
aaa authentication ssh console LOCAL
aaa authentication telnet console LOCAL
http server enable
http 0.0.0.0 0.0.0.0 NAZCO
snmp-server host NAZCO 10.10.10.196 community ***** version 2c
no snmp-server location
no snmp-server contact
snmp-server community *****
snmp-server enable traps snmp authentication linkup linkdown
snmp-server enable traps syslog
snmp-server enable traps ipsec start stop
snmp-server enable traps entity fru-insert
snmp-server enable traps remote-access session-threshold-exceeded
snmp-server enable traps connection-limit-reached
snmp-server enable traps cpu threshold rising
snmp-server enable traps ikev2 start stop
snmp-server enable traps nat packet-discard
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca trustpool policy
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
6c2527b9 deb78458 c61f381e a4c4cb66
quit
telnet timeout 5
ssh scopy enable
ssh 172.16.200.0 255.255.255.0 NAZCO
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0
management-access NAZCO
dhcp-client update dns server both
dhcpd dns
dhcpd update dns both
dhcpd address 172.16.200.20-172.16.200.89 NAZCO
dhcpd dns 172.16.20.1 172.16.4.1 interface NAZCO
dhcpd lease 1048575 interface NAZCO
dhcpd update dns both interface NAZCO
dhcpd enable NAZCO
threat-detection basic-threat
threat-detection statistics
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
ssl encryption rc4-sha1 aes128-sha1 aes256-sha1 3des-sha1
username admin password bZmVDHuxUzzxS3yz encrypted privilege 15
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect icmp
inspect icmp error
class class-default
user-statistics accounting
service-policy global_policy global
prompt hostname context
service call-home
no call-home reporting anonymous
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
hpm topN enable
Cryptochecksum:357b7c6f861e8aa9bb3a3674a789b39b
: end
asdm image disk0:/asdm-721.bin
no asdm history enable

Hi
Looks like the AAA configuration is set for local
aaa authentication enable console LOCAL
aaa authentication http console LOCAL
aaa authentication serial console LOCAL
aaa authentication ssh console LOCAL
aaa authentication telnet console LOCAL
Change it to Radius
aaa-server Keefa-Raduis protocol radius
aaa-server Keefa-Raduis (NAZCO) host 172.16.200.10
key *****
radius-common-pw *****
for example :
aaa authentication telnet console Keefa-Raduis LOCAL
Now when you will do telnet to using Radius credentials, Its Should work, If radius goes down you can use LOCAL username and password as fallback method.
Cheers!
Minakshi(Do rate the helpful post)

Unable to start guest OS in Hyper-V on Server 2012 R2

I get the following error trying to start any guest OS in Hyper-V Manager:
"An error occurred while attempting to start the selected virtual machine(s)::
'TestVM' failed to start.
Virtual Machine 'TestVM' could not be started because the hypervisor is not running.
'TestVM' failed to start. (Virtual machine ID xxxxxxxxxxxx)
Virtual machine 'TestVM' could not be started because the hypervisor is not running (Virtual machine ID xxxxxxxxxxxx).
The following actions may help you resolve the problem:
1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then
turn it back on. Resetting the physical computer is not sufficient.)
2) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically."
Host (Physical) Hardware:
- Supermicro X9SRL-F, BIOS Rev 3.0a (current) with Intel Virtualization enabled and Execute Disable Bit enabled
supermicro.com/products/motherboard/Xeon/C600/X9SRL-F.cfm
- Intel Xeon E5-2620 CPU
http://ark.intel.com/products/64594/Intel-Xeon-Processor-E5-2620-15M-Cache-2_00-GHz-7_20-GTs-Intel-QPI
- 96GB ECC DDR3 RAM
Host Software:
- Server 2012 R2 DataCentre with update 1 (clean install)
- Hyper-V role installed
All hardware supports virtualization and was previously running VMWare VSphere 5.5 without problem.
The BIOS settings for Intel Virtualization and Execute Disable Bit are both enabled.
The server has been physically shutdown and powered off numerous times, but still doesn't work.
I've read Ben Armstrong's notes on setting the Hypervisor Launch type in BCDEdit
Here's the current Boot Configuration Data
Windows Boot Manager
identifier {bootmgr}
device partition=\Device\HarddiskVolume8
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
bootshutdowndisabled Yes
default {current}
resumeobject {06bff081-9477-11e4-ab74-9faf6fe9d444}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows Server 2012 R2
locale en-US
inherit {bootloadersettings}
recoverysequence {06bff083-9477-11e4-ab74-9faf6fe9d444}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {06bff081-9477-11e4-ab74-9faf6fe9d444}
nx OptOut
hypervisorlaunchtype Auto
Here's my System Info:
OS Name Microsoft Windows Server 2012 R2 Datacenter
Version 6.3.9600 Build 9600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name HYPER1
System Manufacturer Supermicro
System Model X9SRL-F
System Type x64-based PC
System SKU To be filled by O.E.M.
Processor Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz, 2001 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3.0a, 5/12/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Supermicro
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Workstation
Secure Boot State Unsupported
PCR7 Configuration Not Available
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume8
Locale Australia
Hardware Abstraction Layer Version = "6.3.9600.17196"
User Name Not Available
Time Zone AUS Eastern Daylight Time
Installed Physical Memory (RAM) 96.0 GB
Total Physical Memory 96.0 GB
Available Physical Memory 93.0 GB
Total Virtual Memory 110 GB
Available Virtual Memory 107 GB
Page File Space 14.0 GB
Page File C:\pagefile.sys
Hyper-V - VM Monitor Mode Extensions
Yes
Hyper-V - Second Level Address Translation Extensions
Yes
Hyper-V - Virtualization Enabled in Firmware
Yes
Hyper-V - Data Execution Protection
Yes
I do have the following two errors in the Hyper-V server role event log that occur at system startup, but can't find any info on it:
Log Name: System
Source: Microsoft-Windows-Hyper-V-Hypervisor
Date: 12/01/2015 3:35:37 PM
Event ID: 63
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPER1
Description:
Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase 0x5), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more
information or updated firmware.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-Hypervisor" Guid="{52FC89F8-995E-434C-A91E-199986449890}" />
<EventID>63</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-01-12T04:35:37.814579300Z" />
<EventRecordID>3955</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>HYPER1</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Phase">0x5</Data>
</EventData>
</Event>
Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
Source: Microsoft-Windows-Hyper-V-VMMS
Date: 13/01/2015 11:21:23 AM
Event ID: 15350
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: HYPER1
Description:
The virtualization infrastructure driver (VID) is not running.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
<EventID>15350</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-01-13T00:21:23.250980100Z" />
<EventRecordID>181</EventRecordID>
<Correlation />
<Execution ProcessID="1512" ThreadID="1576" />
<Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
<Computer>HYPER1</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
</VmlEventLog>
</UserData>
</Event>
I've also read a number of other threads that haven't assisted including:
- https://social.technet.microsoft.com/Forums/en-US/396c882f-2cc8-4bc8-804d-eec75c0b8066/virtual-machine-could-not-be-started-because-the-hypervisor-is-not-running
- https://social.technet.microsoft.com/Forums/windowsserver/en-US/85b323a8-9233-49b9-bc38-e28e7a4222c6/server-2008-hypervisor
There is no event ID 3112 in the event log, so this MS KB article (2490458) is not relevant
Following pics attached show BIOS settings for CPU and Virtualization / Execute Bit Disable settings:

I recently ran into this. The person had made a modification to the System Properties of the Windows operating system.
System Properties > Advanced > Performance > Settings ...
On the Performance Options window, select the Data Execution Prevention tab. Ensure Turn on DEP for all programs and services except those I select is the option selected. He had the other option selected. The only way to get it to get it working
was to change the setting, uninstall Hyper-V, reboot, install Hyper-V, reboot.
. : | : . : | : . tim

SharePoint 2013 OS: Windows Server 2008 R2 vs Windows Server 2012 Standard

Hi Team,
We are thinking on upgrading from SharePoint 2010 to SP 2013 soon. I have been researching about the server OS I should install as host, and it seems that SharePoint 2013 is fully compatible by now with both Windows Server 2008 R2 Standard + SP1 and
Windows Server 2012 Standard. In my opinion we should go with server 2012, but Windows server 2008 is the norm here at our organization and our Infrastructure team seems reluctant to upgrade servers to 2012 yet.
My question is, what SharePoint or Windows 2012 features will we miss if we decide to stay on Windows 2008? What are the perks (selling points) of going with 2012 over 2008? (besides the obvious Microsoft support range extension).
Thanks!
-Rob.

If you stay on Windows Server 2008 R2 you will enter the extended/out of support phase sooner, of course. You will miss out on IIS improvements, although in practical terms it may not mean much.
There are extra patches required for a 2008 R2 deployment that are not needed on 2012 for SharePoint 2013. But other than that, I think the other big issue is that mostly in the community, you'll find people running Server 2012 which means issues are better
'known' by the community, versus 2008 R2 in combination with SharePoint 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Extending a Partition on Server 2012

Similar Messages

Maybe you are looking for