Microsoft Technology

  • Active Directory
  • DNS  
  • DFS Concept
      • Best Practise with Different MS Server Version
      • Known Issues, Troubleshooting and Resolution  
  • DHCP
  • HYPER-V
      • Installation, Configuration
      • Advanced Configuration
      • SCVMM
      • Known Issue, Troubleshooting and Resolution 
  • SCCM/SCOM
      • Installation and Configuration on Different MS Server Version
      • Advanced Configuration
      • Known Issues, Troubleshooting and Resolution
  • MS Azure
      • Introduction
  • Exchange Serve
      • Installation and Configuration of Different version
      • Advanced Configuration
      • Known Issues, Troubleshooting and Resolution


Before Proceeding with the home lab there are couple of things which you need to keep handy.

1. Note down all Static IP details
2. All User name and password
3. Keep Handy all software ISO and tools to make your lab easier and peaceful ( 2008R2, 2012, Openfiler, ESXi5.5, Vcenter Installation ISO, putty, Winscp)


Now started Installation of 2008R2 vm in workstation but lost 1 hours due to this error. Tried most of all tools and recommended links to resolve but the solution worked for me is use new 2008R2 ISO.















The Fresh Installation will start and it will give you the above error at 38%. Most of links and tools suggested to disable  execute disable bit in bios and once i disable this there is problem with ESXI.


    7 comments:

    1. jacku5 September 2016 at 02:49

      Namashkar, Requesting for the details of the relationship or dependency between DHCP, DNS and AD. And troubleshooting.

      ReplyDelete
    2. Piyush Srivastava5 September 2016 at 10:16

      Sure Friend, working on this part also.

      ReplyDelete
    3. Piyush Srivastava5 September 2016 at 16:44

      Sure, can i have your aim. its only for interest purpose or any specific requirement. That will help me to create a scenario for you.

      ReplyDelete
    4. Jaril6 October 2016 at 01:17

      In my infra, I have set to the Windows Update policy to prevent automatic reboot after the Windows Update installation. But still 4 for servers rebooting, even they are having an active session also. I got event ID 22 for the server restart. There is common policy for servers. I have checked multiple scenarios like kept a active and ideal session time out. But failed, server still restarting after the patch installation. Seeking a best for the problem. If required I will provide the event logs

      ReplyDelete
    5. Jaril6 October 2016 at 01:21

      Requesting you to check the feasibility to include option to share or attach files in the blog. That will help to share events and snaps. The blog we can make more user friendly.

      ReplyDelete
    6. Unknown13 April 2017 at 08:27

      Hello Team,
      In our infra, we have scheduled a script to pull the locked machine details to fix the account lock out issues. But some times we received empty machine details and not configure that script in all 57 domains.
      So could you please share your idea if any to configure automatically logoff if an account is idle for more than 30 minutes.
      It would be really helpful to fix this issue.
      Many Thanks in advance..!
      Regards,
      SARAVANA
      spmca13@gmail.com

      ReplyDelete
      Replies
      1. Piyush Srivastava13 April 2017 at 21:00

        Thanks for your comment here,
        i email you some steps to perform this auto logoff.
        but make sure to test first in Test environment before applying in to PROD.
        any further query or details please let us know.

        Thanks
        All4Techie team

        Delete

    Subscribe to: Posts (Atom)