ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Exchange 2016 Install Issue

    Scheduled Pinned Locked Moved IT Discussion
    59 Posts 7 Posters 4.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DashrenderD
      Dashrender @G I Jones
      last edited by Dashrender

      @G-I-Jones said in Exchange 2016 Install Issue:

      @Dashrender said in Exchange 2016 Install Issue:

      @G-I-Jones said in Exchange 2016 Install Issue:

      you mean you were not making this a VM? crazy man, crazy!

      Nah man, remember I was waiting on the H730P? I was hoping to get up a bare metal in the meantime, but that didn't work out.

      Sure, but even a temp box should still be a VM. No reason to really ever make it bare metal.

      If I was building a temp Exchange box, I'd slap whatever hypervisor on that box first - make a VM, install windows Server and then Exchange... no different than the ultimate location where I want to host Exchange. Do it this way makes it cake to move to the new hardware - just shut down the VM, transfer it over, import if needed, start it up and go! no worrying about doing a P2V...

      They have identical PERC Adapters, lol.

      that doesn't really matter - it could have been a desktop for the temp machine - assuming it had enough storage for your needs đŸ˜‰
      this is because you're migrating the VM, which is mostly if not entirely, hardware agnostic...

      1 Reply Last reply Reply Quote 0
      • G I JonesG
        G I Jones @Dashrender
        last edited by

        @Dashrender said in Exchange 2016 Install Issue:

        Just so I understand the environment.

        You had/have
        AD server - still have
        Exchange 2013 - now gone
        Exchange 2016 - now gone

        Is that right?

        Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with

        AD server
        Exchange server

        Question - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?

        I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.

        DashrenderD dbeatoD 2 Replies Last reply Reply Quote 0
        • DashrenderD
          Dashrender @G I Jones
          last edited by

          @G-I-Jones said in Exchange 2016 Install Issue:

          @Dashrender said in Exchange 2016 Install Issue:

          Just so I understand the environment.

          You had/have
          AD server - still have
          Exchange 2013 - now gone
          Exchange 2016 - now gone

          Is that right?

          Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with

          AD server
          Exchange server

          Question - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?

          I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.

          Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?

          G I JonesG 1 Reply Last reply Reply Quote 0
          • G I JonesG
            G I Jones @Dashrender
            last edited by

            Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?

            Money.

            DashrenderD 1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender @G I Jones
              last edited by

              @G-I-Jones said in Exchange 2016 Install Issue:

              Is there a reason you are returning to onsite Exchange instead of moving to O365 or some other hosted solution?

              Money.

              As in you already have the Exchange licenses, so it's mostly a non cash setup situation?

              G I JonesG 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender
                last edited by

                How many users do you have? how many workstations? How many file shares - are permissions used a lot in those file shares?

                perhaps, it would be worthwhile to start your AD all over again?

                G I JonesG 1 Reply Last reply Reply Quote 0
                • G I JonesG
                  G I Jones @Dashrender
                  last edited by

                  As in you already have the Exchange licenses, so it's mostly a non cash setup situation?

                  Nail on the head.

                  1 Reply Last reply Reply Quote 0
                  • G I JonesG
                    G I Jones @Dashrender
                    last edited by G I Jones

                    @Dashrender said in Exchange 2016 Install Issue:

                    How many users do you have? how many workstations? How many file shares - are permissions used a lot in those file shares?

                    perhaps, it would be worthwhile to start your AD all over again?

                    I'm gonna power through this build first and see how it goes.

                    1 Reply Last reply Reply Quote 0
                    • dbeatoD
                      dbeato @G I Jones
                      last edited by

                      @G-I-Jones said in Exchange 2016 Install Issue:

                      @Dashrender said in Exchange 2016 Install Issue:

                      Just so I understand the environment.

                      You had/have
                      AD server - still have
                      Exchange 2013 - now gone
                      Exchange 2016 - now gone

                      Is that right?

                      Assuming it is, now you're trying to add a new Exchange server back into this environment, on a new server, so you'll end up with

                      AD server
                      Exchange server

                      Question - do you still have the old data from Exchange 2013/2016? that you need to put into this new Exchange server?

                      I don't. We're considering it a complete loss. Silver lining is we'll get the funding to protect ourselves now, and the opportunity to build everything into VM's.

                      So why not setup a fully new AD domain and reinstall Exchange there then? It would be the best course of action as it will be clean.

                      G I JonesG 1 Reply Last reply Reply Quote 0
                      • G I JonesG
                        G I Jones @dbeato
                        last edited by

                        @dbeato We may have to, but like I said I'm going to power through this build first, and we'll see how it goes.

                        dbeatoD 1 Reply Last reply Reply Quote 0
                        • dbeatoD
                          dbeato @G I Jones
                          last edited by

                          @G-I-Jones said in Exchange 2016 Install Issue:

                          @dbeato We may have to, but like I said I'm going to power through this build first, and we'll see how it goes.

                          Do it side by side. Setup another AD in another Server and work through it. I bet the new one will go much faster.

                          G I JonesG 1 Reply Last reply Reply Quote 0
                          • G I JonesG
                            G I Jones @dbeato
                            last edited by G I Jones

                            @dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a blank canvas if it comes to that.

                            JaredBuschJ 1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch @G I Jones
                              last edited by

                              @G-I-Jones said in Exchange 2016 Install Issue:

                              @dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a fresh canvas if it comes to that.

                              This is a horrible idea. Rolling back AD is almost never a good idea.

                              G I JonesG DashrenderD 2 Replies Last reply Reply Quote 1
                              • G I JonesG
                                G I Jones @JaredBusch
                                last edited by

                                @JaredBusch please elaborate.

                                DashrenderD 1 Reply Last reply Reply Quote 0
                                • DashrenderD
                                  Dashrender @JaredBusch
                                  last edited by

                                  @JaredBusch said in Exchange 2016 Install Issue:

                                  @G-I-Jones said in Exchange 2016 Install Issue:

                                  @dbeato My plan is to just roll back the snapshot of the AD we have now to when we first built it pre-Exchange. Giving me a fresh canvas if it comes to that.

                                  This is a horrible idea. Rolling back AD is almost never a good idea.

                                  OMG - THIS, one million times this!

                                  1 Reply Last reply Reply Quote 0
                                  • DashrenderD
                                    Dashrender @G I Jones
                                    last edited by

                                    @G-I-Jones said in Exchange 2016 Install Issue:

                                    @JaredBusch please elaborate.

                                    AD is extremely time sensitive. By default, a domain joined PC who's time is off more than 5 mins from the AD server, can not authenticate because the server will think it's being attacked.

                                    Computers also generate their own passwords for connectivity to AD - and they update these passwords completely autonomously. So any machine that has updated to a new password since your snapshot, would no longer work on the domain.

                                    There is a process for restoring an old version of AD into a network - but it is rather complex (and something I've never done or seen done).

                                    G I JonesG 1 Reply Last reply Reply Quote 0
                                    • G I JonesG
                                      G I Jones @Dashrender
                                      last edited by

                                      @Dashrender said in Exchange 2016 Install Issue:

                                      @G-I-Jones said in Exchange 2016 Install Issue:

                                      @JaredBusch please elaborate.

                                      AD is extremely time sensitive. By default, a domain joined PC who's time is off more than 5 mins from the AD server, can not authenticate because the server will think it's being attacked.

                                      Computers also generate their own passwords for connectivity to AD - and they update these passwords completely autonomously. So any machine that has updated to a new password since your snapshot, would no longer work on the domain.

                                      There is a process for restoring an old version of AD into a network - but it is rather complex (and something I've never done or seen done).

                                      I literally just rolled back my AD/DC a week ago. The process was very smooth. You just change the time and Boot/re-add every machine to the domain. The latter being the most timely, but it’s really easy.

                                      That’s my experience at least.

                                      DashrenderD 2 Replies Last reply Reply Quote 0
                                      • DashrenderD
                                        Dashrender @G I Jones
                                        last edited by

                                        @G-I-Jones said in Exchange 2016 Install Issue:

                                        @Dashrender said in Exchange 2016 Install Issue:

                                        @G-I-Jones said in Exchange 2016 Install Issue:

                                        @JaredBusch please elaborate.

                                        AD is extremely time sensitive. By default, a domain joined PC who's time is off more than 5 mins from the AD server, can not authenticate because the server will think it's being attacked.

                                        Computers also generate their own passwords for connectivity to AD - and they update these passwords completely autonomously. So any machine that has updated to a new password since your snapshot, would no longer work on the domain.

                                        There is a process for restoring an old version of AD into a network - but it is rather complex (and something I've never done or seen done).

                                        I literally just rolled back my AD/DC a week ago. The process was very smooth. You just change the time and Boot/re-add every machine to the domain. The latter being the most timely, but it’s really easy.

                                        That’s my experience at least.

                                        yeah - you had to readd every PC to the domain - that's the crazy part...

                                        Curious - why did you roll it back?

                                        And if you have so few machines that you don't mind rejoining them all - then really - Just start over. There is Zero benefit to sticking with an AD that has any potential to have problems.

                                        As more or less indicated by my earlier question - the amount of file shares/printer shares/file permissions and devices joined to the domain kinda tell you how much of a PITA setting up a new domain will be, because you have to rebuild all of those things.

                                        G I JonesG 2 Replies Last reply Reply Quote 0
                                        • DashrenderD
                                          Dashrender @G I Jones
                                          last edited by

                                          @G-I-Jones said in Exchange 2016 Install Issue:

                                          @Dashrender said in Exchange 2016 Install Issue:

                                          @G-I-Jones said in Exchange 2016 Install Issue:

                                          @JaredBusch please elaborate.

                                          AD is extremely time sensitive. By default, a domain joined PC who's time is off more than 5 mins from the AD server, can not authenticate because the server will think it's being attacked.

                                          Computers also generate their own passwords for connectivity to AD - and they update these passwords completely autonomously. So any machine that has updated to a new password since your snapshot, would no longer work on the domain.

                                          There is a process for restoring an old version of AD into a network - but it is rather complex (and something I've never done or seen done).

                                          I literally just rolled back my AD/DC a week ago. The process was very smooth. You just change the time and Boot/re-add every machine to the domain. The latter being the most timely, but it’s really easy.

                                          That’s my experience at least.

                                          I have 120 PCs in my environment - I would never want to roll back AD and have to run around like a chicken with my head cut off rejoining those to my domain.

                                          G I JonesG scottalanmillerS 2 Replies Last reply Reply Quote 0
                                          • G I JonesG
                                            G I Jones @Dashrender
                                            last edited by

                                            Curious - why did you roll it back?

                                            I rolled it back because of the encryption attack.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post