Learning Windows server 2012 R2 & 2012 core

Hi,
How do i configure a fast and standard solution with 1domain (Windows
Server 2012 R2) and 1subdomain(Windows Server 2012 Core) implemented with a webserver and security for dns?
Thx

Hi
Maybe this can help,
Nslookup test:
cmd => nslookup => set type=mx => host.net.
Organizational unit:.be
Active directory users and computers openen => rmb op domeinnaam => new => organtizational unit aanmaken => Protection uitvinken
Computer Manueel toevoegen aan domein:
1)DNS veranderen naar 192.168.1.1 van het domein zelf
2)Add-Computer -domainname host -cred administrator@host -passthru -verbose
GPO voor chrome installeren:
1)Group policy management => in OU PC's => new policy aanmaken
2)rmb policy en klik edit
3)onder computer => software => new package => pad ingeven waar je msi bestand hebt gezet van chrome => \\S1\netlogon\msi\chrome.msi
4)client heropstarten en aanmelden met domeingebruiker => powershell => Restart-Computer
5)mapje waar MSI in zit => security => domain controller (user) toevoegen met volledig beheer
GPO voor browser block chrome:
3)block listed urls..
4)op client gpupdate
Failed login events:
1)Group policy instellen op OU Servers: Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy\ ==> Failed logins aanzetten
2)gpupdate /force
1)powershell
2)get-windowsfeature => install-windowsfeature SMTP-Server
3)Internet information services => S1 => Domain RMB => properties => Acces tab => Relay => Add => Group computers => IP: 192.168.1.1 subnet 255.255.255.0 => Ok => ok
3b)Eens afmelden en aanmelden met fout wachtwoord zodat er een log geschreven wordt met audit failure in de security log van event viewer
4)Eventviewer security log => op failed audit log RMB => attach => Geef andere naam => next => next start program => program: powershell.exe =>
open the propery dialog aanvinken
5)Run wheter user is logged in or not aanvinken => tabke conditions: start the task only if AC power afvinken! => ok => paswoord administrator ingeven
6)powershell: get-executionpolicy => resultaat moet remotesigned zijn => view tabke => script pane aanzetten =>
Script geven: $smtpServer = ìsmtp2.school.beî
$msg = New-Object Net.Mail.MailMessage
$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$msg.From = ì[email protected]î
$msg.ReplyTo = [email protected]î
$msg.To.Add([email protected]î)
$msg.subject = ìhacking attempt?î
$msg.body = ìlogin/pwd failure on S1.î
$smtp.Send($msg)
7)Script opslaan in mapje op C schijf => powershell cd naar mapje met script => ls commandoTo configure the time source for the forest
8)Task scheduler openen => naar event viewer tasks => login => rmb properties => actions => powershell.exe edit => add arguments: -command "C:\Script\login.ps1" => ok => password admin ingeven
9)Testen
*Op welke manier kan je je MX records controleren met NSLOOKUP
cmd => nslookup => set type=mx => host.net.
*Commando powershell om Client toe te voegen aan het domein:
Add-Computer -domainname host -cred administrator@host -passthru -verbose
Best practice analyzer:
1)Server manager => klik op dns en op ADDS => Scroll naar onder tot bij BPA => Task start scan => bekijk resultaten:
Vraagje: Welke suggesties zou je kunnen oplossen:
DNS server should have scavenging enabled
De PDC emulator master moet geconfigureerd worden
1)To configure a domain controller in the parent domain as a reliable time source
*W32tm /config /reliable:yes /update
2)To configure the time source for the forest
*w32tm /config /computer:s1.host.net /manualpeerlist:ntp.belnet.be /syncfromflags:manual /update
Tijd moet gelijk zijn van S1 en S2!!
Corefig opstarten in powershell:
1)cd C:\corefig
2)execution policy aanpassen: Set-ExecutionPolicy bypass
3).\corefig.ps1
4)naam veranderen in corefig
Commando om S2 toe te voegen aan het domein in de OU servers:
1)DNS instellen
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.1.1
2)Toevoegen aan OU servers
Add-Computer -domainname sdhost -cred administrator@host -OUPath "OU=Servers,OU=OU,DC=Host,DC=net"
Herstarten
OPPASSEN HIERMEE ALS S2 ZELF DC MOET WORDEN!
Voorzie je server van de DNS-rol via windows powershell:
1)Import-Module Servermanager
2)Get-WindowsFeature
2)Add-WindowsFeature "DNS" -restart
Remoteaccess:
S1 remote access geven voor administrators bij active directory
view => advanced features enablen
=> Remote management users => HOST\Administrator toevoegen met full rechten
=> Remote Desktop users => HOST\Administrator toevoegen met full rechten
Bekijk welke firewall regel op dit moment Remote Management nog blokkeert en laat
die communicatie toe:
1)Op S2 in powershell: Configure-SMRemoting.exe -enable
2)op S1 => Server manager => manage => add servers => S2 ingeven => ok
3)Active directory installeren op s2 via add roles (via S1)
4)S2 promoveren to domain controller
5)credentials van s1 gebruiken => naam subdomain 'premium'
6)DSRM passwoord: P0wnerken
7)PREMIUM
DNS instellen van s2 zelf
Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses 192.168.1.2
C2)DNS server instellen op S2 : 192.168.1.2
Toevoegen aan domein premium.host.net => inloggen met admin account van s2 domein
herstarten van C2
Maak†van†deze†tweede†server†nu†een†domeincontroller†voor†het†nieuwe†domein
ìpremiumî.†Daar†zijn†twee†werkwijzen†voor.†Zoek†deze†methodes†op†en†noteer†deze
summier†hieronder:
- Werken met DCPROMO.exe
- Werken met GUI vanop S1
Je†mag†zelf†kiezen†welke†methode†je†toepast.†Noteer†hier†wel†de†commandoís†die†je
toepast:
Werken met GUI: new existing domain to current forest => naam PREMIUM
Netwerkkaarten toevoegen:
VCLOUD => Niet customizen!!!
Firewall disablen S2:
netsh firewall set opmode disable
Op S1 => chrome => ip in url : https://192.168.1.150:446 => proceed => logingegevens:
naam: openfiler
pass: password
Services => CIFS / NFS => Enable => Start
manage volumes => 1GB volume => start cyl = 1, end cyl = 128 => ongeveer 1GB
Add volume group => NFS als naam en 1GB volume toevoegen => Add volume => naar onder scrollen:
Naam: NFS
Bestandssysteem: EXT4 kiezen
*Add new physical volume 10GB: MINSTENS 35 CYLINDERS TUSSENLATEN!!!!
Start cyl = 164, end cyl = 1469, is ongeveer 10GB
Volume groups => Nieuwe aanmaken met SMB als naam => Add volume => volume selecteren en toevoegen => naar uw smb volume group gaan
=> SMB volume kiezen => naam: SMB => MAX Geheugen => EXT4 bestandssysteem
1)Clocksettings zetten via ntp server: ntp.belnet.be (Moet gelijk zijn met domaincontroller waarin je hem toevoegd)
2)DNS zetten van S2
Hostname: of
Primary DNS: 192.168.1.2
Secondary DNS: 192.168.1.1
Gateway: 192.168.1.254
3)Accounts:
Expert view!
*Use windows domain controller and authentication aanvinken
Security Mode: Active directory
Domain / workgroup: PREMIUM
Domain controllers: s2.premium.VAhost.net
ADS realm: PREMIUM.HOST.NET
Join domain: aanvinken
Administrator username: Administrator
Administrator password: Azerty123
*Naar onder scrollen tot kerberos 5: Aanvinken
Realm: premium.host.net
KDC: s2.premium.host.net
Admin server: s2.premium.VAhost.net
Share aanmaken:
1)Shares => klikken op SMB / NFS => Nieuwe subfolder aanmaken: SMBshare / NFSshare
2)subfolder klikken => maak share => bij rechten naar beneden scrollen => Domain admins: PG & RW, Domain users: RO
3)Update
Systeem beveiliging:
1)system => Network access configuration => Nieuw netwerk toevoegen
Name: Sharenetwork
Network/host: 192.168.1.0
Netmask: 255.255.255.0
Type: Share
2)Update
Protocol aanzetten:
Shares => subfolder smbshared => Volledig vanonder scrollen => SMB/CIFS protocol op rw zetten
Connect to share met:
root
Azerty123
Connect Z-schijf met SMB share:
1)RMB op SMB share
2)Map network drive
3)Pad SMB share intypen
4)connecten met share account of finish 1)Private storage en manueel ip adres ingeven
Beveiliging backup:
1)Active directory van S1
2)OP s1 zelf volledig nieuwe OU: "TEMP Accounts" aanmaken => accidentally delete afzetten!!
3)2USers aanmaken die lid zijn van de groep ("member of") Guest
4)Op S1 => C schijf => nieuwe map map aanmaken en delen
5)Op advanced sharing van gedeelde map => Guest 1 Full control => Everyone alleen read rechten
6)Testen op client of je op Guest1 tekstbestand kan aanmaken en via Guest2 op die share map niet.
7)Als het werkt Guest1 verwijderen en bekijk sharing permissions op Guest1 map
*Wat stel je vast bij verwijderen Guest1 via active directory:
De guest account wordt vervangen door een ander account met een lange naam
die full control heeft over de map
8)Guest1 terug opnieuw aanmaken, wat stel je vast?
Guest1 heeft geen rechten meer over de map en de aangemaakte account blijft staan
Recycle BIN:
1)Open Active directory administrative center
2)Klik op uw domein links
3)Rechts => enable Recycle Bin
4)Verwijder Guest1 op AD
5)Guest1 komt te staan bij deleted users/objects op Recycle Bin
6)Mogelijkheid om te restoren
7)Delete OU Temp accounts => Lukt niet onmiddellijk => Omdat er nog objecten in zitten
*Zoek op welke technieken je kan toepassen om een backup te nemen van je Active Directory. Bekijk uiteraard ook welke 2 manieren
er zijn om een backup van je AD terug te plaatsen (Authoritative en non-authoritative):
-13.1.1 Authoritative Restore
Dit proces herstelt de AD na bc een wijziging die ongedaan gemaakt moet worden.
AD wordt hersteld vanaf de backup, de backup overschrijft dan alle andere DC's met eventuele nieuwere informatie.
-13.1.2 Non-Authoritative Restore
Terugzetten van gegevens van de backup. Nadien ontvangt de DC updates van andere DC's die gemaakt zijn sinds de backup.
Backup S1:
Eerst probleem openfiler oplossen:
1)openfiler opstarten vanuit vmcloud
2)cd /etc/samba
3)vim smb.conf (toevoegen: strict allocate = yes) => eerst i voor insert => opt einde escape => :wq voor opslaan
4)/etc/init.d/smb restart
Backup zelf
1)Install windows backup in server manager => add roles => features
2)Open windows backup
3)Action => backup once
4)Different options => Custom kiezen => System State backuppen
5)Remote disk kiezen
6)pad share: \\of\smb.smb.SMBshare
7)Als backup mislukt, de aangemaakte files door de backup manueel verwijderen en backup terug opnieuw proberen
!!!Als openfiler ineens verdwijnd van domein, moet je de tijd nakijken van beiden systemen (moeten gelijk zijn met max 5min verschil)
Restore backup (authoritatief ingesteld)
http://technet.microsoft.com/ru-ru/library/cc816878(v=ws.10).aspx
1)Herstart de domeincontroller in Directory Services Restore Mode Remotely
=> run => Msconfig.msc => stapkes staan in url: http://technet.microsoft.com/ru-ru/library/cc794729(v=ws.10).aspx
2)Restore uw ADDS van je backup a.d.h.v. een non-authoritatieve restore.
Dit zorgt ervoor dat de domeincontroller terug in de staat komt waarop de objecten die verwijderd zijn
er terug bijstaan.
http://technet.microsoft.com/ru-ru/library/cc794755(v=ws.10).aspx
in cmd:
=>wbadmin get versions -backuptarget:\\of\smb.smb.SMBshare
=>wbadmin start systemstaterecovery -version:12/03/2013-12:37 -backuptarget:\\of\smb.smb.SMBshare -quiet
3)Markeer objecten als authoritatief zodat ze niet worden overschreven bij het restoren door synchronisatiefouten
tussen de verschillende domeinen.
http://technet.microsoft.com/ru-ru/library/cc816813(v=ws.10).aspx <== hieraan beginnen
=> open run => ntdsutil
=> activate instance ntds => enter
=> authoritative restore => enter
=> restore subtree "OU=Stagiairs,DC=Host,DC=net" => enter
=> quit => enter
=> Start terug op met de domaincontroller in normale modus dus dsrm opstartmode uitschakelen: Safe boot uitvinken
Nakijken of beide OU's Stagiairs en Guests er nog staan
(In dit geval is OU guests wel verwijderd doordat we maar 1 DC hebben dus de informatie
wordt niet gesynchroniseerd met een 2de DC)
- Debian Machine toevoegen:
Netwerkgegevens: NIC0 / Private management network / static - manual / IP = 192.168.1.3
Als Machine aangemaakt is, nieuwe netwerkkaart toevoegen:
NIC1 / Private storage network / static - manual / IP = 172.16.0.13
op Debian machine:
1)su - => enter => pass: Azerty123 => enter
2)commando: pico /etc/network/interfaces
Voeg volgende lijntjes toe aan het bestand
iface eth0 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.254
iface eth1 inet static
address 172.16.0.13
netmask 255.255.255.0
CTRL + O (opslaan) => CTRL + X (afsluiten)
3)pico /etc/resolv.conf
veranderd de bestaande lijntjes naar deze:
domain host.net
search host.net
nameserver 192.168.1.1
4)ifdown / ifup van eth0/eth1
IPV6 instellen:
Zelf gekozen ULA subnet:
fdac:1fff:b0b0 (tot dit gedeelte mag random gegenereerd worden vanaf 'fd')
Subnet 1: fdac:1fff:b0b0:4bd0:: /64
Subnet 2: fdac:1fff:b0b0:4bd1:: /64
/sbin/ip
Remote settings toewijzen voor domain users aan clients (en eventueel toevoegen aan domein als dit nog niet gebeurt is)
IPV6 instellen via Netwerkinstellingen (Default gateway openlaten)
        NIC0                    NIC1
S1: fdac:1fff:b0b0:4bd0::1 /64            fdac:1fff:b0b0:4bd1::11 /64
dns: ::1                    dns: fdac:1fff:b0b0:4bd1::11
S2: fdac:1fff:b0b0:4bd0::2 /64            fdac:1fff:b0b0:4bd1::12 /64
(dns: ::1)                (dns: fdac:1fff:b0b0:4bd1::12)
Openfiler: fdac:1fff:b0b0:4bd0::150 /64        fdac:1fff:b0b0:4bd1::1 /64    
S3: fdac:1fff:b0b0:4bd0::3 /64            fdac:1fff:b0b0:4bd1::13 /64
C1: fdac:1fff:b0b0:4bd0::101 /64
dns: S1
C2: fdac:1fff:b0b0:4bd0::102 /64
dns: S2
Voor windows server core:
*powershell
    netsh interface ipv6 add address "Ethernet" fdac:1fff:b0b0:4bd0::2
    netsh interface ipv6 add address "Ethernet 2" fdac:1fff:b0b0:4bd1::12
Voor linux: (zowel openfiler als debian)
VOOR DEBIAN 7 (alleen ifup commando gebruiken niet ifdown):
/sbin/ip -6 addr add fdac:1fff:b0b0:4bd0::3/64 dev eth0 (voor debian)
/sbin/ip -6 addr add fdac:1fff:b0b0:4bd1::13/64 dev eth1 (voor debian)
of statisch in /etc/network/interfaces:
iface eth0 inet6 static
address fdac:1fff:b0b0:4bd0::3
netmask 64
iface eth1 inet6 static
address fdac:1fff:b0b0:4bd1::13
netmask 64
pico /etc/resolv.conf => lijntjes toevoegen
=> domain host.net
=> search host.net
=> nameserver 192.168.1.1
=> nameserver fdac:1fff:b0b0:4bd0::1
VOOR OPENFILER eth0: vim /etc/sysconfig/network-scripts/ifcfg-eth0
=> IPV6_AUTOCONF=no
=> IPV6INIT=yes
=> Toevoegen: fdac:1fff:b0b0:4bd0::150/64
VOOR OPENFILER eth1: vim /etc/sysconfig/network-scripts/ifcfg-eth1
=> IPV6_AUTOCONF=no
=> IPV6INIT=yes
=> Toevoegen: fdac:1fff:b0b0:4bd1::1/64
~~ /sbin/ip -6 addr add fdac:1fff:b0b0:4bd0::150/64 dev eth0 (voor openfiler)
~~ /sbin/ip -6 addr add fdac:1fff:b0b0:4bd1::1/64 dev eth1 (voor openfiler)
Risico's gedeelde application pool:
    -1 proces per application pool (=>zwaar proces dat veel resources nodig heeft)
        (als dit proces vastloopt alle websites geimpacteerd)
    -gebruikers kunnen in principe aan elkaars bestanden
1)IIS installeren op S2 via server manager op S1
2)Role services in setup, volledig vanonder => management service aanvinken (dit staat remote management toe)
3)Op S1 Web server zoeken en enkel van IIS de management console installeren zodat IIS van S2 beheerbaar is
4)Powershell op S2:
Invoke-command -ScriptBlock{Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\WebManagement\Server -Name EnableRemoteManagement -Value 1}
Invoke-command -ScriptBlock {Set-Service -name WMSVC -StartupType Automatic}
Invoke-command -ScriptBlock {Start-service WMSVC}
In IIS manager op S1 => Add connection => S2.premium.sdhost.net => account: administrator van S2
In IIS Manager => Sites => new Website, 2 website aanmaken
    -'klant1.sdhost.net' Physical path => C:\inetpub\wwwroot\Klant1 => hostname = Klant1.host.net
    -'klant2.sdhost.net' Physical path => C:\inetpub\wwwroot\Klant2 => hostname = Klant2.host.net
In DNS A-record toevoegen:
    -hostname: www
    -IP: 192.168.1.2
Voor toegang via IPv6 ook een AAAA-record toevoegen:
    -hostname: www
    -IP: fdac:1fff:b0b0:4bd0::2
Voor elke site ook een een CNAME-record aanmaken:
    -Alias name: klant1, FQDN: www.host.net
    -Alias name: klant2, FQDN: www.host.net
In deze standaardopstelling schuilen enkele risicoís. Geef twee risicoís die de huidige
configuratie (gedeelde application pool) met zich mee kan brengen:
- Als je een website hebt die zwaar CPU belastend is (zoals foto's herschalen) heeft dit ook effect op je andere websites
- Omdat je websites binnen dezelfde apppool zitten hebben ze eenzelfde identiteit en kun je geen aparte permissies opzetten.
GROUP MANAGEMENT SERVICE ACCOUNT:
New-ADServiceAccount IISPool1 -DNSHostName s1.amhost.net -PrincipalsAllowedToRetrieveManagedPassword Administrator -KerberosEncryptionType RC4, AES128, AES256
Install-ADServiceAccount IISPool1
Maybe you can do this tutorial to, it is a tuto for learning DFS & DNSSEC..
Wat betekent de optie “dnssecok”
    -> Deze optie stelt de dnssecOK bit in voor deze query
    -> Dit verteld de server that de client dnssec verstaat en dat deze server hiervan gebruik kan maken met deze client
Krijg je een bevestiging dat dit een secure antwoord is? (RRSIG)
    -> Neen want de zone is nog niet gesigneerd
Controleer of de client C1 ingesteld is om secure responses af te dwingen bij zijn DNS
caching server: get-dnsclientnrptpolicy. Resultaat?
    -> Het resultaat is niks, vermoedelijk omdat er geen instellingen zijn hiervoor
Probeer opnieuw een request op C1 voor S1 met Resolve­DNSName. Is het signeren
van de zone voldoende om secure antwoorden te krijgen op de client?
    -> Er komt opnieuw geen RSIG record dus dit is niet voldoende
Om secure DNS responses op de client voor het domein securezone.lab af te dwingen
wordt in het domein Host.net een GPO ingesteld. (nieuwe GPO voor hele domein).
zoek op en stel deze GPO in voor responses van securezone.lab.
    -> default domain policy -> Edit =>    -> Computer Configuration > Policies > Windows Settings > Name Resolution Policy.
    "In the details pane, under Create Rules and To which part of the namespace does this rule apply, choose Suffix from the drop-down list and type sec.contoso.com next to Suffix."
    "On the DNSSEC tab, select the Enable DNSSEC in this rule checkbox and then under Validation select the Require DNS clients to check that name and address data has been validated by the DNS server checkbox."
    "In the bottom right corner, click Create and then verify that a rule for sec.contoso.com was added under Name Resolution Policy Table."
    => GPupdate /force uitvoeren
    => Dan kan de policy bekeken worden
Je zorgt er uiteraard ook voor dat deze policy toegepast werd op de client (C1) en controleer dit opnieuw met get-dnsclientnrptpolicy.
    => GPupdate /force
    => get-dnsclientnrptpolicy => levert hetzelfde resultaat als op de server
Opnieuw: Resolve­DnsName s1.securezone.lab ­server S1 ­dnssecok Wat krijg je als antwoord te zien? Wat is de oorzaak?
(Distribueer) Kopieer de trust achor data van de secure.lab zone op S2 naar S1 en importeer die op de DNS van S1 als trusted anchor. (keyset­securezone.lab)
    http://technet.microsoft.com/en-us/library/hh831411.aspx
opnieuw: Resolve­DnsName s1.securezone.lab ­server S1 ­dnssecok Krijg je nu een (beveiligd antwoord)?
    ->Ik krijg nu een beveiligd antwoord van de DNS server gesigneerd door securezone.lab met geldigheidstermijn
p23 Distributed File System
Installeer op beide server de “file services role”.
    -> Add roles and features
    -> File services
        -> DFS
Maak een namespace aan (DOCUMENTATION) in je domein hOst.net. Stel de share­permissions zo in dat de groep ‘auteurs’ schrijfrechten heeft. gewone gebruikers
mogen enkel leesrechten hebben.
    -> DFS manager
    -> Namespaces => Add namespace
maak een folder aan in de namespace DOCUMENTATION met als naam PDF
    -> Add folder
maak een tweede target aan voor de PDF folder
    -> Add target to folder
stel replicatie in tussen de twee folder targets. De inhoud wordt vanaf nu dus gesynct.
    -> Automatisch bij 2de target volg de wizard
Welke andere stappen zijn nodig om een volledig redundant DFS systeem op te zetten?
    -> De folder moeten via DFS geschared staan
    -> De replicatie moet ingesteld worden
maak een diagnostisch raport aan over hoe replicatie gebeurt, en corrigeer eventue vastgestelde problemen.
    -> Rechtermuisknop op de replication object
    -> Create diagnostic report
    -> kies de reports
stel quota’s in. In de map PDF maak je een subfolder CATALOGS aan, maar zorg dat die niet groter dan 10MB kan worden. Stel hiervoor een harde limiet in.
    -> install FSRM bij file services
    -> klik quotas => add quota => kies het bestand
    -> nieuwe quota => 10mb hard aanvinken
    -> save
    http://technet.microsoft.com/en-us/library/cc875787(v=ws.10).aspx
omdat we willen vermijden dat de volledige bandbreedte ingenomen wordt door DFS,beperken we de replication speed tot 2MBps.
    -> Klik op de replication -> rechterkolom kies vor edit replication group
    -> Stel de 2MBps in

Similar Messages

  • How do you repair ntoskrnl.exe error or system error in windows server 2008 and 2012

                              
    hi,
    can you repair system file errors like  ntoskrnl.exe in windows server 2008 and 2012  like   like before  in windows server 2003 ?
     the steps were  repairing ntoskrnl.exe  error in windows server 2003
    1- have a 2003 cd and from that cd  start recovery console and copy from i386 directory ntldr and ntdetect.com to  windows /system32 directory on the  server and then repairing
    2- MBR with fixmbr command  and then  rebuild BOT.INI file  with bootcfg/rebuild . 
    now my question  is how you repair or solve such problem with ntoskrnl.exe error  in windows server 2008 and windows server 2012
    thanks
    johan
    h.david

    first this wil take a lot of time for windows 2008 and 2012 ,
    and what about windows 2003 I thing this has no startup repair
    thanks
    johan
    h.david
    What will take a lot of time? Repair or clean install? These days one can standup a new VM and have an operating system on it in around 20 minutes or so.
    Correct server 2003 is file based deployment and completely different OS from repair perspective as well.
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Migration on windows server 2003 to 2012 r2 by using IIS 6.0 what are parameters are changed means supported and non suported parameters and configurations?

    In my project am going to migrate windows server 2003 to 2012 r2 by using IIS 6.0? what are the parameters are changed and what are the parameters are not supported and what are the modules need to change?
    Please give the related answer as soon as posssibule. that is more help for me?
    Thanks,
    vamsikrishna.

    1. This seems to be incomplete description.
    2. You can enable legacy technologies while installing roles and features.
    3. For application pool(s) you should consult respective developer/vendor team(s) for help.
    Regards
    Milos

  • ADPrep Migration from Windows Server 2003 to 2012 Foundation Server fails with error 0x80004005

    Hi all,
    Having a problem the forums and Google have been unsuccessful in helping me with. Server is Windows 2003 R2, migrating to Windows Server 2012 foundation.  Have tried the AD Migration on the new 2012 Foundation server both as a standalone server
    and a domain server member before running the migration.  I get the following error:
    ADPrep execution failed --> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning
    I've checked the ADprep logs and have found the following:
    [2013/01/22:11:15:01.000]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x0 
    [2013/01/22:11:15:01.001]
    Adprep checked to verify whether operation cn=abd97102-88dd-4013-a009-0e2c2f967ff6,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local has completed.
    [Status/Consequence]
    The operation GUID already exists so Adprep did not attempt to rerun this operation but is continuing.
    [2013/01/22:11:15:01.001]
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local.
    [2013/01/22:11:15:01.001]
    LDAP API ldap_search_s() finished, return code is 0x20 
    [2013/01/22:11:15:01.001]
    Adprep verified the state of operation cn=134428a8-0043-48a6-bcda-63310d9ec4dd,cn=Operations,cn=ForestUpdates,CN=Configuration,DC=apl,DC=local. 
    [Status/Consequence]
    The operation has not run or is not currently running. It will be run next.
    [2013/01/22:11:15:01.021]
    Adprep was unable to complete because the call back function failed. 
    [Status/Consequence]
    Error message: Unable to access the computer "SERVER.apl.local". The network path was not found.
     (0x80070035).
    [User Action]
    Check the log file ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information.
    DSID Info:
    DSID: 0x1811132a
    winerror = 0x1f
    NT BUILD: 9200
    NT BUILD: 16384
    [2013/01/22:11:15:01.021]
    Adprep was unable to update forest information. 
    [Status/Consequence]
    Adprep requires access to existing forest-wide information from the schema master in order to complete this operation.
    [User Action]
    Check the log file, ADPrep.log, in the C:\Windows\debug\adprep\logs\20130122111500 directory for more information. 
    We did have AVAST Antivirus installed on the server but this was removed.  Any idea's?
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

    Hi Biswajit et. al., thanks for your help thus far, it is greatly appreciated...
    Unfortunately I had already disabled the NIC's on both hosts.  They currently remain disabled.  I've just tried turning off IPv6 as well and no luck.
    PortQry came back fine (I think) :)
    =============================================
     Starting portqry.exe -n server.apl.local -e 135 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 135 (epmap service): LISTENING
    Using ephemeral source port
    Querying Endpoint Mapper Database...
    Server's response:
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[dhcpcsvc]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001d40.00000001]
    UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint
    ncalrpc:[LRPC00001448.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[OLE4EF57D32A0DB45F9A64653468D7C]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000012ac.00000001]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncacn_np:\\\\SERVER[\\pipe\\tapsrv]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[tapsrvlpc]
    UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint
    ncalrpc:[unimdmsvc]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncalrpc:[W32TIME_ALT]
    UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
    ncacn_np:\\\\SERVER[\\PIPE\\W32TIME_ALT]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 6bffd098-a112-3610-9833-46c3f874532d 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[OLE7C4E3B9B79D8492CBA384F149E08]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncacn_ip_tcp:10.0.0.3[1111]
    UUID: 5b821720-f63b-11d0-aad2-00c04fc324db 
    ncalrpc:[DHCPSERVERLPC]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 3d267954-eeb7-11d1-b94e-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 12d4b7c8-77d5-11d1-8c24-00c04fa3080d 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncalrpc:[LRPC00000480.00000001]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_np:\\\\SERVER[\\pipe\\HydraLsPipe]
    UUID: 493c451c-155c-11d3-a314-00c04fb16103 
    ncacn_ip_tcp:10.0.0.3[1092]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[OLE43978C47C6F54B5499302BAB2F50]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_ip_tcp:10.0.0.3[1090]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncalrpc:[LRPC00001060.00000001]
    UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 
    ncacn_np:\\\\SERVER[\\pipe\\WinsPipe]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service
    ncalrpc:[LRPC00000d10.00000001]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API
    ncalrpc:[LRPC00000d10.00000001]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[OLE92F283EA5C2F497093CE6A52B7D8]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncacn_ip_tcp:10.0.0.3[1067]
    UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE
    ncalrpc:[LRPC00000d10.00000001]
    UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076 
    ncacn_ip_tcp:10.0.0.3[1048]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncalrpc:[LRPC000004d4.00000001]
    UUID: 906b0ce0-c70b-1067-b317-00dd010662da 
    ncacn_ip_tcp:10.0.0.3[1032]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[audit]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[securityevent]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[dsrole]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncalrpc:[NTDS_LPC]
    UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ab 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[audit]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[securityevent]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[dsrole]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncalrpc:[NTDS_LPC]
    UUID: 12345778-1234-abcd-ef00-0123456789ac 
    ncacn_http:10.0.0.3[1027]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[audit]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[securityevent]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[dsrole]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncalrpc:[NTDS_LPC]
    UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[audit]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[securityevent]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[dsrole]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncalrpc:[NTDS_LPC]
    UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-01234567cffb 
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\lsass]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[audit]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[securityevent]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_np:\\\\SERVER[\\PIPE\\protected_storage]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[dsrole]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_ip_tcp:10.0.0.3[1026]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[NTDS_LPC]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncacn_http:10.0.0.3[1027]
    UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint
    ncalrpc:[OLE8B33809919104CE5B44970B01637]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[wzcsvc]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 1ff70682-0a51-30e8-076d-740be8cee98b 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[wzcsvc]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[wzcsvc]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncalrpc:[OLE396AE4FBEFCC4DD2B44D0F0A3691]
    UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 
    ncacn_np:\\\\SERVER[\\PIPE\\atsvc]
    UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
    ncalrpc:[DNSResolver]
    Total endpoints found: 125
    ==== End of RPC Endpoint Mapper query response ====
    portqry.exe -n server.apl.local -e 135 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 389 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 389 (ldap service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:54 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 (unknown service): LISTENING or FILTERED
    Using ephemeral source port
    Sending LDAP query to UDP port 389...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    UDP port 389 is LISTENING
    portqry.exe -n server.apl.local -e 389 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 636 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 636 (ldaps service): LISTENING
    portqry.exe -n server.apl.local -e 636 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3268 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3268 (msft-gc service): LISTENING
    Using ephemeral source port
    Sending LDAP query to TCP port 3268...
    LDAP query response:
    currentdate: 01/28/2013 14:11:57 (unadjusted GMT)
    subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=apl,DC=local
    dsServiceName: CN=NTDS Settings,CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    namingContexts: DC=apl,DC=local
    defaultNamingContext: DC=apl,DC=local
    schemaNamingContext: CN=Schema,CN=Configuration,DC=apl,DC=local
    configurationNamingContext: CN=Configuration,DC=apl,DC=local
    rootDomainNamingContext: DC=apl,DC=local
    supportedControl: 1.2.840.113556.1.4.319
    supportedLDAPVersion: 3
    supportedLDAPPolicies: MaxPoolThreads
    highestCommittedUSN: 1310788
    supportedSASLMechanisms: GSSAPI
    dnsHostName: SERVER.apl.local
    ldapServiceName: apl.local:[email protected]
    serverName: CN=SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=apl,DC=local
    supportedCapabilities: 1.2.840.113556.1.4.800
    isSynchronized: TRUE
    isGlobalCatalogReady: TRUE
    domainFunctionality: 2
    forestFunctionality: 2
    domainControllerFunctionality: 2
    ======== End of LDAP query response ========
    portqry.exe -n server.apl.local -e 3268 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 3269 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 3269 (msft-gc-ssl service): LISTENING
    portqry.exe -n server.apl.local -e 3269 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 53 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 53 (domain service): LISTENING
    UDP port 53 (domain service): LISTENING
    portqry.exe -n server.apl.local -e 53 -p BOTH exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 88 -p BOTH ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 88 (kerberos service): LISTENING
    UDP port 88 (kerberos service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 88 -p BOTH exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 445 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 445 (microsoft-ds service): LISTENING
    portqry.exe -n server.apl.local -e 445 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 137 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 137 (netbios-ns service): LISTENING or FILTERED
    Using ephemeral source port
    Attempting NETBIOS adapter status query to UDP port 137...
    Server's response: MAC address 000423c733ec
    UDP port: LISTENING
    portqry.exe -n server.apl.local -e 137 -p UDP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 138 -p UDP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    UDP port 138 (netbios-dgm service): LISTENING or FILTERED
    portqry.exe -n server.apl.local -e 138 -p UDP exits with return code 0x00000002.
    =============================================
     Starting portqry.exe -n server.apl.local -e 139 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 139 (netbios-ssn service): LISTENING
    portqry.exe -n server.apl.local -e 139 -p TCP exits with return code 0x00000000.
    =============================================
     Starting portqry.exe -n server.apl.local -e 42 -p TCP ...
    Querying target system called:
     server.apl.local
    Attempting to resolve name to IP address...
    Name resolved to 10.0.0.3
    querying...
    TCP port 42 (nameserver service): LISTENING
    portqry.exe -n server.apl.local -e 42 -p TCP exits with return code 0x00000000.
    Jason.
    Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

  • Can't record web session in Web Application Transaction Monitoring using IE10 (Tried under Windows Server 2008R2 and 2012)

    Hi,
    In Operations Manager Console 2012 SP1 including RU2 I am trying to record a web session in Web Application Transaction Monitoring.
    I have check that:
    The add-on (Microsoft Web Recorder Helper) 64bit is Enabled.
    The 64bit version of IE10 is running/launched. See this link for how to modify your registry key if needed:  http://kevingreeneitblog.blogspot.co.uk/2012/01/scom-2012-recording-web-browser-session.html
    I have tried both on a Windows 2008R2 and 2012 server, but the recorder is not showing up as can been seen from Kevin's Blog (link above).
    Any Ideas?

    I managed to get this working on both Windows 8 IE10 and server 2012 IE10. Tested on SCOM 2012 SP1 UR2 and UR3. I've done this process in lab and production several times so hopefully this helps you out.
    Checklist:
    1. Ensure that the 64bit IE10 is launching when the "start web-capture" is started in SCOM.
    2. Enable IE10 internet options:
    a: Advanced - Security - Enable Enhanced Protected Mode
    b: Advanced - Browsing - Enable third-party browser extensions
    3. Close all running IE sessions and open the Registry Editor
    4. Registry Change (No reboot needed)
    - Browse to the following regkey:
    HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main
    - Add a new DWORD called TabProcGrowth and set it to 0
    5. Registry Change (No reboot needed)
    - Browse to the following regkey:
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64\
    -You should see two subkeys labeled: (These are the cached BHO IE objects related to the Web Recorder)
    {00021493-0000-0000-C000-000000000046}
    {00021494-0000-0000-C000-000000000046}
    - Delete only the above two mentioned keys (This will force IE to recache them next launch)
    6. Try to start the web capture again from SCOM 2012 SP1.
    7. When IE10 Launches enable the add-on again if you are prompted.
    8. If you still don't see the Web-Recorder pane in IE you can now show it by:
     - View - Explorer bars - Web Recorder

  • Bind Mavericks to Windows Server 2012 R2 domain

    I have a Windows 2012 R2 domain controller (only one in the domain) with the forest and domain in native (not mixed) mode.
    I am trying to bind a Mavericks Macbook Pro to the domain.
    I have checked that I can ping the domain and domain controller by name and IP address.
    I have set the NTP on the Macbook to use the domain controller as the time source.
    I even set the "Prefer this domain server" to the domain controller.
    When I attempt bind the Macbook, the time tested message of "Authentication server could not be contacted."
    Any suggestions?  Something about Windows Server 2012 R2 that I am missing?  I admit that I am just learning Windows
    Server 2012 R2, so it is possible my lack of knowledge of it is the adding to the problem.
    Thank you in advance!

    I have 3 Server 2012 DC's here on my network.  No issues binding Macs to the DC.  I haven't had the time to roll out R2 DCs yet, but will be doing so shortly as I am now done with some other upgrades.  I would roll out one right now so I can test this for you, but don't have the time...sorry man.
    One of the most important thing with AD is DNS.  1 of my 3 AD's is my DNS and DHCP server.  I have not had to mess with any special settings, just let my Mac get it's IP from the DC and then bind away.  Are your windows machines (if you have any) on the same LAN able to bind?  Also make sure the account you are logged into the mac with is an Admin on the local mac. 
    Remove all the custom info you put in, keep it simple, I have never had to fill in any of those details, and make sure you use the FQDN of your DC (host.domain.com).  Once you put in the FQDN, does the utility recognize the Domain and then ask for the AD admin credentials?  If yes, then thats a good sign. 
    Let me know if it's still not working.  Also make sure you are using the correct login and password, the admin of your DC. 
    Is your DC virtual or Physical?  Do you have the firewall enabled on your DC?  Are you using wireless or wired? 
    I'm sure you will get this... S12R2 is really sweet, all my Hyper-V hosts are S12R2. 

  • Windows Internal Database on Windows Server 2012 - How can I find out what role or feature is using it?

    We have setup many roles and features and apparently one of them is using the Windows Internal Database (WID). We have had some events logged for WID and need to troubleshoot them. But we are not sure which role/feature is using it. How can I find
    this out?

    Hi,
    Several components of Windows Server 2008 and 2012 use Windows Internal Database for their data storage: Active Directory Rights Management Services, Windows System Resource Manager, UDDI Services, Active Directory Federation Services 2.0, IPAM and Windows
    SharePoint Services.
    Which role did you setup or what is the error message did you received?
    Regards.
    Vivian Wang

  • Windows server 2012 as primary DC and DNS server and windows server 2003 as secondary DC and DNS

    Migration from windows server 2003 AD DC and DNS server to windows server 2012 R2,
    Cannot I set up Windows server 2012 R2 as primary DC and DNS  , windows server 2003 as secondary DC and DNS ? (for backup server when server 2012 fail, user can continue to login and access internet services)

    You can mix both as long as your Forest and Domain Functional level are Windows Server 2003. However, I would like to bring your attention to this blog about known problems when mixing DCs with Windows Server 2003 and 2012 R2 OS:
    http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Server 2012 and 2012 R2 do not allow access to all 7 optical SAS drives?

    The following problem occurs with Windows Server 2008 R2, 2012 and 2012 R2, Datacenter or Standard. 
    I have an external SAS enclosure with seven optical drives and one hot-swap SAS/SATA bay that connects using two SFF-8088 connectors (no internal SAS expander, etc.).  The purpose is to use the seven bluray writers to write multiple copies of a large
    database simultaneously.  The optical drives are also occasionally used to read datasets that come on multiple discs (usually 8-12 per dataset and up to 15 datasets at a time).  Because of the volume, more optical drives are definitely better. 
    Regardless of the type of SAS controller used to connect this enclosure, some significant functionality is always missing.
    For writing, it is best to connect directly to the optical drives (which do their own buffering) so a HBA would seem better than a hardware RAID controller.  I have tried several HBAs, including LSI-9211, LSI-9240-IT, Dell H310-IT.  In all cases,
    Windows only sees four DVD drives and the hot-swap bay.  The drives Windows sees work perfectly for reading and writing.  MegaRAID Storage Manager (LSI controller software) sees all seven optical drives and the hot-swap bay.  LSI says this
    must be a Windows problem.  Strangely, if I remove (any) three optical drives and replace them with hot-swap bays, all eight devices are recognized by Windows.
    If I use a true RAID controller (tried LSI-9260, Dell H800, Dell H810, HP 812P, IBM 5015), windows and MSM see all seven drives and the hot-swap bay, reads from the optical drives are fine, but writing large discs times out (presumably because of buffering
    by the RAID card) so I can't write DVDs.
    Is there a way to get Server to recognize all seven optical drives on an HBA?  Ideally, I'd like to add several of these enclosures but I can't even get one working properly!
    The system is a Tyan (Dell) MB with dual Xeon E5-2620s and 64Gb RDIMM.  Currently includes LSI-9260 (2Tb SAS 10k in RAID 0), Dell H810 (32Tb SAS in RAID 6), and LSI-9211 (optical enclosure + 3Tb hot-swap).  Just installed Server 2012 R2 Datacenter
    for testing.
    Any help would be greatly appreciated.

    I've had the experience of working as a validation engineer for Intel, who at the time was developing a SAS/SATA storage controller chipset for thier new xeon processors. The chipset was included in their motherboard offerings. I validated the linux driver,
    which is now included in the linux kernel as of the 3.x series kernel.
    My first question is, what type of SAS enclosure are you using for your optical drives/hot swap bay? You will be surprised at how many enclosures don't actually provide a 100% direct-attached storage configuration, and instead opt to work as a mini expander
    instead. In our validation, we tested several SAS enclosures, and we found several that even though they were advertised as direct-attached enclosures, by inspecting the data transmission with a SAS protocol analyzer we found communication over SMP (Serial
    Management Protocol).
    To ensure it is NOT the enclosure causing the anomaly, i'd connect the 7 optical drives directly to each storage controller unit (or sff-8087). These cards can support around 256 devices via expander attached configuration, as that is how many sas addresses
    the scu's can support. Either way, they can only support a maximum of 8 devices direct-attached (4 per SCU). I would use a multi-line SFF-8087 SATA breakout cable to directly connect your optical drives to the HBA, 4 on SCU0 and the other 3 on SCU1.
    I find it strange that LSI's storage manager can see all of the drives, but windows cannot. Since the SAS protocol allows for the ATAPI cmd set to be sent via scsi commands, the only thing I can think of is if windows can only recognize a certain amount
    of SAS-addresses utilizing the ATAPI cmd set. Technically, it should only be limited by the number of devices the hba can support, and in either LSI thats 256. Otherwise the enclosure may be doing something funny with the initiator (SCU), where one initiator
    may take precedence over the other. Again, testing a direct connection with a SFF-8087 SATA breakout cable will eliminate the enclosure as a factor.
    I can understand from a developer perspective for the desire to have windows recognize the devices instead of relying on the lsi storage app. Firstly, that app is monstrous and unwieldy. Secondly, it does not allow for customized solutions/scripting to fully
    access the optical devices, since you have to interact w/ lsi's storage mgr. 3rd, this should simply work if MS is fully compliant with the SAS protocol.
    Finally, I want to make sure everyone is aware that a fully compliant 6G SAS compliant device will support SSP (Serial SCSI protocol), SMP (Serial Management Protocol), and STP (Sata Tunneling Protocol). STP basically defines how SATA devices can inter-operate
    within the sas fabric by tunneling ATA commands via the SCSI cmd set. This is a basic functionality guaranteed within the overall SAS protocol; if your HBA supports SAS & SATA, it will support SSP, SMP, and STP frames (this is usually always listed on
    the HBA), and therefore it will fully support SATA devices. A SAS device will support SSP & SMP. A SATA-only HBA will support the ATA cmd set only (and thus, cannot inter-operate within a SAS fabric).
    Please note that at the very least, a direct-attached configuration should provide the number of Storage Controller Units x 4 fully working SATA devices (generally each internal SFF-8087 is a scu, most HBA's have a min of 2 SCU's, and 4 directly addressable
    devices per SCU (8 direct attached devices total). Generally, any issues that will arise from SATA devices will be the result of expander-attached configurations. There are many points a SATA device can experience errors in a expander-attached configuration,
    from the routing mechanism being utilized (table vs subtractive), to the type of expander being used (fan-out vs edge expander). Expanders will generally at least support 1 method of routing, if not both, and may or may not support multi-level configurations
    (this is specifically dependent on the hba). It was not uncommon in our testing to come across expanders that would work great w/ SAS & SATA w/ 1 level expander, but fail to communicate with SATA devices past 2 or more levels. This falls on the responsibility
    of the HBA, specifically the driver for the OS.
    More Info on SATA Tunneling Protocol (STP): 
    http://www.serialstoragewire.net/Articles/2004_0225/developer_article_2_feb.html

  • Window server on intel core duo

    is window server installed on intel core duo.how it is installed

    Perhaps you are misunderstanding something about Apple computers.
    All Apple computers, including those with the Intel Core Duo processors, come with Mac OS X as the preinstalled operating system.
    Only recently, Apple has released a beta version of Boot Camp, which is software that will allow you to partition your hard drive for the purpose of installing Windows XP on a seaparate partition, thus creating a dual boot system. Boot Camp includes drivers for Windows XP which allows Windows to run on the Apple hardware.
    You can't simply install any version of Windows on Apple hardware.
    You need to install Boot Camp first. Boot Camp does not have the drivers for Windows 2003 server, so you will probably not be able to run it successfully.

  • Undefined error updating Adobe AIR on Windows Server 2008

    I am trying to upgrade from Adobe AIR version 2.7.1.1961 to version version 3.1.0.4880.
    The operating system is Windows Server 2008 Standard  - SP1
    I am logged on as the administrator and shortly in the upgrade process, I receive a Window stating:
    Sorry an error has occurred
    An error occured while install Adobe AIR. Installation may not be allow by your administrator.
    Please contact your administrator
    Following is the install log:
    [2012-02-15:15:56:56] Runtime Installer begin with version 3.1.0.4880 on Windows Server 2008 x86
    [2012-02-15:15:56:56] Commandline is:
    [2012-02-15:15:56:56] Installed runtime (2.7.1.19610) located at c:\Program Files (x86)\Common Files\Adobe AIR
    [2012-02-15:16:02:46] Relaunching with elevation
    [2012-02-15:16:02:46] Launching subprocess with commandline c:\users\admini~1\appdata\local\temp\1\air704f.tmp\adobe air installer.exe -ei
    [2012-02-15:16:02:46] Runtime Installer begin with version 3.1.0.4880 on Windows Server 2008 x86
    [2012-02-15:16:02:46] Commandline is: -stdio \\.\pipe\AIR_15060_0 -ei
    [2012-02-15:16:02:46] Installed runtime (2.7.1.19610) located at c:\Program Files (x86)\Common Files\Adobe AIR
    [2012-02-15:16:02:46] Starting silent runtime update. Updating runtime from version 2.7.1.19610 to version 3.1.0.4880
    [2012-02-15:16:02:46] Installing msi at c:\users\admini~1\appdata\local\temp\1\air704f.tmp\setup.msi with guid {FE23D063-934D-4829-A0D8-00634CE79B4A}
    [2012-02-15:16:02:46] Error occurred during msi install operation; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-15:16:02:46] Rolling back install of c:\users\admini~1\appdata\local\temp\1\air704f.tmp\setup.msi
    [2012-02-15:16:02:46] Rollback complete
    [2012-02-15:16:02:46] Exiting due to error: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-15:16:02:46] Exiting due to error: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-15:16:02:46] Runtime Installer end with exit code 7
    [2012-02-15:16:04:17] Runtime Installer end with exit code 7
    Other notes that might be of use is that I have tried to uninstall Adobe AIR with a similar error message.
    I am hoping someone can provide some insight on how to resolve this situation.

    Thanks for the links above.
    I downloaded and run the Microsoft Install and Uninstall Fix It. Thinking there could be issues with the current version of AIR, I ran the utility and chose to uninstall the current version of AIR; and was successful.
    I followed up by restarting the computer and then go to the Adobe AIR download page. When I try to install the new version, it get basically the same error message.  The log file from the install is below.
    [2012-02-16:18:07:14] Runtime Installer begin with version 3.1.0.4880 on Windows Server 2008 x86
    [2012-02-16:18:07:14] Commandline is:
    [2012-02-16:18:07:14] No installed runtime detected
    [2012-02-16:18:07:19] Relaunching with elevation
    [2012-02-16:18:07:19] Launching subprocess with commandline c:\users\princi~1\appdata\local\temp\air11d3.tmp\adobe air installer.exe -ei
    [2012-02-16:18:07:19] Runtime Installer begin with version 3.1.0.4880 on Windows Server 2008 x86
    [2012-02-16:18:07:19] Commandline is: -stdio \\.\pipe\AIR_2648_0 -ei
    [2012-02-16:18:07:19] No installed runtime detected
    [2012-02-16:18:07:19] Starting silent runtime install. Installing runtime version 3.1.0.4880
    [2012-02-16:18:07:19] Installing msi at c:\users\princi~1\appdata\local\temp\air11d3.tmp\setup.msi with guid {FE23D063-934D-4829-A0D8-00634CE79B4A}
    [2012-02-16:18:07:19] Error occurred during msi install operation; beginning rollback: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-16:18:07:19] Rolling back install of c:\users\princi~1\appdata\local\temp\air11d3.tmp\setup.msi
    [2012-02-16:18:07:19] Rollback complete
    [2012-02-16:18:07:19] Exiting due to error: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-16:18:07:19] Runtime Installer end with exit code 7
    [2012-02-16:18:07:19] Exiting due to error: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="1601" errorID=0]
    [2012-02-16:18:07:22] Runtime Installer end with exit code 7
    Finally, when I try to run the fixit tool again, it is of no practical use as there is no program to repair.
    Again,  I am hoping someone can provide some insight on how to resolve the current situation

  • Cisco Prime Infrastructure 1.2 on Windows Server/Hyper-V

    Hi Everyone,
    In Entriprise environment while designing a BYOD solution we need to integrate ISE3315 with CPI 1.2. I know that Cisco ISE software either runs on 3315 platform or other option is virtual appliance (which is VMware based). Now problem is that we have Hyper-V environment as standard so I need to go with ISE-3315. Here my concern is to I install CPI 1.2 on Hyper-V, or on a Windows Server (2008 or 2012) based machine. Is that doable?
    Any help, suggessions would be warmly welcomed.
    Thanks,
    Azhar...

    Cisco Prime LMS will slowly be phased out in favor of Cisco Prime Infrastructure and hence there are no new mainline releases are planned to provide support to new Hardware or virtualization support.
    However, Prime LMS do support Hyper V Virtualization (As an installable in Windows 2008). Please note that Virtualization technologies like, VMWare and Hyper V virtualization systems are not supported in LMS 5000, and LMS 10000 Devices license, in Windows. VMWare Systems are supported in LMS 5000, and LMS 10000 Devices license in Soft Appliance. Virtualization technologies like, VMWare and Hyper V virtualization systems are not supported in LMS 5000, and LMS 10000 Devices license, in Windows. VMWare Systems are supported in LMS 5000, and LMS 10000 Devices license in Soft Appliance.
    For more details on HW and SW requirements for Cisco Prime LMS, please check document here.
    -Thanks
    Vinod

  • I have a solution for DKIM signing in Windows Server

    Hello.
    I have a solution for DKIM signing Keys in Windows Server 2008 and 2012
    Explanation will be long in the forum.
    If someone in need, please contact me by skype ID: sasgroupe
    Thank you

    Hi,
    Nice.
    But is it feature that header is not scroll horizontally ?
    Br, Jari

  • Bug: Flash play freezes on Windows Server = 2008R2

    Description:
    Adobe Flash player version 11.3.300.268 11.3.300.265 caused FireFox x86 on Windows Server 2008 R2, 2012 to freeze with complete repro. It's a edge case for WIndows Servers to run Firefox and flash but I want to raise this issue to have it fixed in the next version.
    Repro steps:
    1. Install Windows Server 2008 R2 or Windows Server 2012 (Microsoft Internal RTM version build 9200 available to Microsoft employees only)
    2. Install Firefox x86 14.0.1
    3. Install flash player 11.3.300.268 OR 11.3.300.265.
    4. Lauch firefox and browse to http://www.flash.com/
    5. Observe Firefox not responsive
    6. Workaround is terminating Firefox by running "Stop-Process -Name Firefox" at Powershell v2
    7. Expect Flash not to freeze firefox.
    8. Temporary Solution: Install Flash Player 11.2.202.235 release or debug version.
    9. Temporary Solution 2: Install flash 11.3.300.268 OR 11.3.300.265 on Internet Explorer.
    Adobe flash support engineers, please investigate into the problem.

    I installed http://labsdownload.adobe.com/pub/labs/flashplatformruntimes/flashplayer11-4/flashplayer11 -4_p2_install_win_pi_080712.exe on Windows Server 2008 R2 (remember it's R2, not just 2008). I launched firefox 14 (32 bit image) and the plugin worked with www.flash.com without problems (plugin as a process in 32 bit image). Do you still need me to file a bug at http://bugbase.adobe.com/ ?

  • E-MU 0404 PCIe Digital Audio System for Windows server

    E-MU 0404 PCIe Digital Audio System for Windows server
    Is it possible use E-MU 0404 PCIe under Windows Server 2008 or 2012?

    Originally Posted by Mike76
    E-MU 0404 PCIe Digital Audio System for Windows server
    Is it possible use E-MU 0404 PCIe under Windows Server 2008 or 2012?
    For windows Server 2008 and Server 2012 you may need enable Desktop Experience Feature
    The Desktop Experience Feature enables a bunch of stuff that is by default present on a desktop OS. Most importantly it includes Themes, Windows Media player and the Aero related features. You will have to enable it form the Server Manager. The "Turn Windows features on or off" / "Add remove windows components" has all been rolled into the Server Manager now.
    Server Manager > Features > Desktop Experience
    Installing the Desktop Experience feature does not enable them. You have to manually set them up.
    After that Windows Server 2008 == Vista x64
    Windows Server 2008 R2 == Windows 7 x64
    Windows Server 2012 == Window 8 x64
    So just use the appropriate desktop drivers - that are available

Maybe you are looking for