Exchange - where email goes to die - The Something Awful Forums

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Exchange - where email goes to die

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

What level and version of Exchange service pack/rollup?

You might need to install language packs to support the swedish

# ? Dec 9, 2014 15:35

Adbot: ADBOT LOVES YOU

# ? May 7, 2024 06:56

Man with Hat: Dec 26, 2007; Open up your Dethday present
It's a box of fucking nothing; Exciting Lemon

Gyshall posted:

What level and version of Exchange service pack/rollup?

You might need to install language packs to support the swedish

Thanks for the response.

Update Rollup 6 for Exchange Server 2010 SP3, I think.

We have loads of accounts with swedish in them, though. It only doesn't work with the accounts created in Powershell, and of those accounts not even the ones without our space letters in them gets the same error.

# ? Dec 9, 2014 15:50

Will Styles: Jan 19, 2005

Man with Hat posted:

Cool, an Exchange thread.

I have a problem when I'm trying to create new email accounts for some new users I made in Active Directory using the AD Powershell thingy.

You might need to specify your parameters directly.

Import-Csv .\NewPeeps.csv -Delimiter : -Encoding UTF7 | % { New-ADUser -Enabled $True -DisplayName $_.DisplayName -Name $_.Name -Description $_.Description -Surname $_.Surname -GivenName $_.GivenName -UserPrincipalName $_.UserPrincipalName -SamAccountName $_.SamAccountName -Office $_.Office -Company $_.Company -AccountPassword (ConvertTo-SecureString PoopBalls -AsPlainText -force) }

At least that's what this technet blog says

# ? Dec 9, 2014 16:22

Man with Hat: Dec 26, 2007; Open up your Dethday present
It's a box of fucking nothing; Exciting Lemon

Will Styles posted:

You might need to specify your parameters directly.

Import-Csv .\NewPeeps.csv -Delimiter : -Encoding UTF7 | % { New-ADUser -Enabled $True -DisplayName $_.DisplayName -Name $_.Name -Description $_.Description -Surname $_.Surname -GivenName $_.GivenName -UserPrincipalName $_.UserPrincipalName -SamAccountName $_.SamAccountName -Office $_.Office -Company $_.Company -AccountPassword (ConvertTo-SecureString PoopBalls -AsPlainText -force) }

At least that's what this technet blog says

I tried that now and sadly I get the same error message when I try to create an exchange account for that AD account.

The account ended up like that though, so I might've done something wrong?

Appreciate the help, by the way!

# ? Dec 10, 2014 09:46

Weird Uncle Dave: Sep 2, 2003; I could do this all day.; Buglord

Man with Hat posted:

I tried that now and sadly I get the same error message when I try to create an exchange account for that AD account.

The account ended up like that though, so I might've done something wrong?

Appreciate the help, by the way!

Most things in PowerShell are $_.property; your screenshot shows things as $._property. Maybe just typos in the script?

# ? Dec 10, 2014 15:47

Man with Hat: Dec 26, 2007; Open up your Dethday present
It's a box of fucking nothing; Exciting Lemon

Weird Uncle Dave posted:

Most things in PowerShell are $_.property; your screenshot shows things as $._property. Maybe just typos in the script?

Yeah, that was me being a dumb moron. It works like you said, with _. instead of ._ to import the accounts with all the cool data in them.

I still get the same error when trying to make them a mailbox, though. I'm gonna see if I can find another server to try it all on, to see if the error is exclusive to the dumb system we have here or not.

# ? Dec 10, 2014 16:37

Will Styles: Jan 19, 2005

Man with Hat posted:

Yeah, that was me being a dumb moron. It works like you said, with _. instead of ._ to import the accounts with all the cool data in them.

I still get the same error when trying to make them a mailbox, though. I'm gonna see if I can find another server to try it all on, to see if the error is exclusive to the dumb system we have here or not.

What happens if you try and use powershell to assign the new user a mailbox?

Enable-Mailbox {username} -Database {mailbox DB} -Verbose {any other paramaters you want to specify}

# ? Dec 10, 2014 19:42

Number19: May 14, 2003; HOCKEY OWNS
FUCK YEAH

So uh...you probably don't want to install Exchange 2010 SP3 CU8:

http://www.infoworld.com/article/2858314/microsoft-windows/microsoft-pulls-exchange-server-2010-sp3-update-rollup-8-kb-2986475.html

quote:

An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.

The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish further updates to this blog post regarding RU8.

This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.

# ? Dec 11, 2014 00:43

Man with Hat: Dec 26, 2007; Open up your Dethday present
It's a box of fucking nothing; Exciting Lemon

Will Styles posted:

What happens if you try and use powershell to assign the new user a mailbox?

Enable-Mailbox {username} -Database {mailbox DB} -Verbose {any other paramaters you want to specify}

The thing is I work at a stupid place. I only have access to the exchange server via the Management Console over Citrix since the exchange server is in another country in our father domain (or whatever it's called) and I'm not trusted.

I'm gonna ask the people who are trusted if they ever tried that when I asked them for help, though, that's a good idea. Thanks.

Edit: Oh, great, they can't do either. Fantastic.

Edit Edit: I just tried the same powershell command with the same csv in a completely different system and got the same error. This is loving weird.

Man with Hat fucked around with this message at 11:44 on Dec 11, 2014

# ? Dec 11, 2014 09:03

Will Styles: Jan 19, 2005

Man with Hat posted:

The thing is I work at a stupid place. I only have access to the exchange server via the Management Console over Citrix since the exchange server is in another country in our father domain (or whatever it's called) and I'm not trusted.

I'm gonna ask the people who are trusted if they ever tried that when I asked them for help, though, that's a good idea. Thanks.

Edit: Oh, great, they can't do either. Fantastic.

Edit Edit: I just tried the same powershell command with the same csv in a completely different system and got the same error. This is loving weird.

Tre-bizarre! I know when I was creating a bunch of users from CSV I used dsadd user and I didn't have any issues assigning them mailboxes. You might want to try that instead of new-aduser.

# ? Dec 11, 2014 18:22

Matt Zerella: Oct 7, 2002; Norris'es are back baby. It's good again. Awoouu (fox Howl)

Number19 posted:

So uh...you probably don't want to install Exchange 2010 SP3 CU8:

http://www.infoworld.com/article/2858314/microsoft-windows/microsoft-pulls-exchange-server-2010-sp3-update-rollup-8-kb-2986475.html

MS has been on fire lately, jfc.

# ? Dec 11, 2014 18:38

Number19: May 14, 2003; HOCKEY OWNS
FUCK YEAH

LmaoTheKid posted:

MS has been on fire lately, jfc.

This is what happens when you lay off most of your QA team.

# ? Dec 11, 2014 18:43

incoherent: Apr 24, 2004; 01010100011010000111001
00110100101101100011011
000110010101110010

I'm pretty sure the skeleton crew of QA for RUs would have a checkbox that says "outlook stops connecting".

# ? Dec 11, 2014 20:27

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

incoherent posted:

I'm pretty sure the skeleton crew of QA for RUs would have a checkbox that says "outlook stops connecting".

they tried to submit the bug but their email wasn't working

# ? Dec 11, 2014 20:31

Number19: May 14, 2003; HOCKEY OWNS
FUCK YEAH

incoherent posted:

I'm pretty sure the skeleton crew of QA for RUs would have a checkbox that says "outlook stops connecting".

You're assuming there's still a skeleton crew.

# ? Dec 11, 2014 20:51

Man with Hat: Dec 26, 2007; Open up your Dethday present
It's a box of fucking nothing; Exciting Lemon

Will Styles posted:

Tre-bizarre! I know when I was creating a bunch of users from CSV I used dsadd user and I didn't have any issues assigning them mailboxes. You might want to try that instead of new-aduser.

You are literally my favorite person in the entire world right now. I had to gently caress about a bit in the CSV to get this method to work but now we can make mailboxes and everything. Thank you so, so much.

If anyone's curious I made this script:

code:

$inputFile = Import-CSV  .\Peeps.csv -Delimiter ";" -Encoding UTF7

foreach($line in $inputFile)
{
    ## need to add quotes around DSN        
    $dsn = "`"cn="+$line.cn+",ou=Forma,ou=users,ou=Company SE,dc=Subdomain,dc=Domain,dc=com`""
    $samid = $line.sAMAccountName
    $ln = $line.surname
    $fn = $line.givenname
    $dn = $line.DisplayName
    ## need to add quotes around display name
    $dn2 = "`"$dn`""
    $upn = $line.UserPrincipalName
    $desc = $line.Description
    $mob = $line.Mobile

    cmd /c "dsadd user $dsn -samid $samid -ln $ln -fn $fn -display $dn2 -upn $upn -mustchpwd yes -pwd PoopBalls -desc $desc -Mobile $mob -disabled no"

    write-host `n
}

And had a CSV file that looked like this, kind of. Except I deleted most of it since it was kind of identifying.

code:

DisplayName;Name;Description;surname;GivenName;UserPrincipalName;SamAccountName;Office;cn;Mobile
Surname, First name SE - subdomainname;Surname, First name SE - subdomainname;"Old Company Name"" ""Department";Surname;First Name;logonname@subdomain.domain.com;logonname;City;Surname First name SE;1234666777

Seriously, thank you. You saved my week. And thanks to everyone else who helped as well, you're good people.

# ? Dec 12, 2014 11:38

Matt Zerella: Oct 7, 2002; Norris'es are back baby. It's good again. Awoouu (fox Howl)

Quick question, removing an ActiveSync partnership is not the same as blocking right?

# ? Dec 22, 2014 17:01

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

Correct. Removing the partnership will re-add it the next time the device tries to sync, assuming credentials haven't changed.

# ? Dec 22, 2014 17:14

Matt Zerella: Oct 7, 2002; Norris'es are back baby. It's good again. Awoouu (fox Howl)

Gyshall posted:

Correct. Removing the partnership will re-add it the next time the device tries to sync, assuming credentials haven't changed.

Thanks.

I'm having a really odd issue with one of my users where ActiveSync wont sync past last Thursday. I just reporduced it on a blank iphone I have here with the same iOS version (8.1.2).

I'm not really seeing any errors on the server either.

e: I switch it to sync one day and it works. What the gently caress.

Matt Zerella fucked around with this message at 17:37 on Dec 22, 2014

# ? Dec 22, 2014 17:26

Filthy Lucre: Feb 27, 2006

I'm in a situation where I need to pull email from a POP3 server to my Exchange Server 2010. The POP3 server and Exchange server are on the same AD domain and the POP3 server is AD integrated.

Anyone know of a POP3 Connector that supports AD integration for Exchange 2010?

# ? Dec 22, 2014 20:21

incoherent: Apr 24, 2004; 01010100011010000111001
00110100101101100011011
000110010101110010

Migrationwiz!

https://www.bittitan.com/products/migrationwiz/mailbox-migration

# ? Dec 22, 2014 20:31

Filthy Lucre: Feb 27, 2006

This isn't a one time migration. A POP3/SMTP server is being placed between our Exchange server and the rest of the world because of office politics.

I looked over the website for Migrationwiz, and it doesn't look like it will do what I need it to. Maybe I missed something?

# ? Dec 23, 2014 17:17

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

You need to look at an Exchange Hub Transport (or Edge Transport) server, but it doesn't sound like that will work. Are you saying you need to pull all email from a POP3 server into a single exchange mailbox?

# ? Dec 23, 2014 18:04

Filthy Lucre: Feb 27, 2006

The email account filthy.lucre@fuckedup.company resides on both the lovely POP3 server and our Exchange Server. The lovely POP3 server is our MX server of record.

When you email filthy.lucre@fuckedup.company, it is received by the lovely POP3 server.
Our Exchange server checks the filthy.lucre@fuckedup.company account via a non-AD aware POP3 connector.
My Outlook connects to our Exchange Server and I get my email.

The problem is, our current POP connector cannot deal with changes in AD passwords. So we either have to disable the password change policy (not feasible), or users have to notify IT staff every time they change their domain password so we can update the POP connector (kill me).

The easiest and best solution would be to return the Exchange server to our MX server of record. Our Exchange Server is functioning perfectly fine and there's no reason to migrate. However, the CEO of some small IT Consulting Business who is "good with computers" plays golf with our parent company's CEO and talked our CEO into buying this lovely POP3 server. Since the company spent the money on this lovely software, it's a corporate decree that we must use it so our CEO doesn't look like an idiot. Meanwhile, we as IT staff, have to keep email/calendaring running as smoothly as possible. Since the POP3 software is poo poo, that means keeping our users on Exchange and letting the Exchange server get the emails from the POP3 server.

The second best solution is to replace our current POP3 connector with one that is AD aware so we don't have to change the password policy or update the POP connector every time someone changes their password.

# ? Dec 23, 2014 19:27

Proud Christian Mom: Dec 20, 2006; READING COMPREHENSION IS HARD

Good luck with that

# ? Dec 23, 2014 19:29

incoherent: Apr 24, 2004; 01010100011010000111001
00110100101101100011011
000110010101110010

Oh man I thought you were doing migration, not that weird rear end configuration.

# ? Dec 23, 2014 19:42

Thanks Ants: May 21, 2004; #essereFerrari

Can't you just pretend you're using the POP thing but just bypass it? How clued up are the people who care?

# ? Dec 23, 2014 19:53

Filthy Lucre: Feb 27, 2006

Enough to be able tell if we're using the lovely POP3 server or not, unfortunately. That was actually my first thought on how to handle this.

# ? Dec 23, 2014 19:56

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

Filthy Lucre posted:

The email account filthy.lucre@fuckedup.company resides on both the lovely POP3 server and our Exchange Server. The lovely POP3 server is our MX server of record.

When you email filthy.lucre@fuckedup.company, it is received by the lovely POP3 server.
Our Exchange server checks the filthy.lucre@fuckedup.company account via a non-AD aware POP3 connector.
My Outlook connects to our Exchange Server and I get my email.

The problem is, our current POP connector cannot deal with changes in AD passwords. So we either have to disable the password change policy (not feasible), or users have to notify IT staff every time they change their domain password so we can update the POP connector (kill me).

The easiest and best solution would be to return the Exchange server to our MX server of record. Our Exchange Server is functioning perfectly fine and there's no reason to migrate. However, the CEO of some small IT Consulting Business who is "good with computers" plays golf with our parent company's CEO and talked our CEO into buying this lovely POP3 server. Since the company spent the money on this lovely software, it's a corporate decree that we must use it so our CEO doesn't look like an idiot. Meanwhile, we as IT staff, have to keep email/calendaring running as smoothly as possible. Since the POP3 software is poo poo, that means keeping our users on Exchange and letting the Exchange server get the emails from the POP3 server.

The second best solution is to replace our current POP3 connector with one that is AD aware so we don't have to change the password policy or update the POP connector every time someone changes their password.

lmao

# ? Dec 23, 2014 20:00

Thanks Ants: May 21, 2004; #essereFerrari

Gyshall posted:

lmao

# ? Dec 23, 2014 20:01

wyoak: Feb 14, 2005; a glass case of emotion; Fallen Rib

If you can setup the lovely POP3 server to route all incoming messages to one mailbox you could have Exchange connect to it as a global mailbox and sort it out based on routing rules. As it stands now it sounds like your IT staff has to know everyone's password which is pretty bad.

Setup Exchange as the MX of record and have it journal everything to the POP3 box. POP3 still gets traffic!

# ? Dec 23, 2014 20:03

Filthy Lucre: Feb 27, 2006

If this weren't happening to me, I'd be laughing, too, because of how hosed up it is.

As it is, I'm mostly swearing and drinking. I've finished off a bottle of Yamazaki 12 and I'm into the Macallan 18 now.

# ? Dec 23, 2014 20:05

Thanks Ants: May 21, 2004; #essereFerrari

I bet this software that is now sat in the middle of all your email traffic has a stellar security record, is well supported, and any issues are patched rapidly!

# ? Dec 23, 2014 20:07

incoherent: Apr 24, 2004; 01010100011010000111001
00110100101101100011011
000110010101110010

Filthy Lucre posted:

Enough to be able tell if we're using the lovely POP3 server or not, unfortunately. That was actually my first thought on how to handle this.

Tickets are down this month! check to see if we've stopped using our messages messaging solution!

# ? Dec 23, 2014 21:53

Will Styles: Jan 19, 2005

Filthy Lucre posted:

When you email filthy.lucre@fuckedup.company, it is received by the lovely POP3 server.
Our Exchange server checks the filthy.lucre@fuckedup.company account via a non-AD aware POP3 connector.
My Outlook connects to our Exchange Server and I get my email.

If people are using Outlook to connect to Exchange what is the purpose of the POP3 server, other than to be an extra hop in maildelivery?

Filthy Lucre posted:

As it is, I'm mostly swearing and drinking. I've finished off a bottle of Yamazaki 12 and I'm into the Macallan 18 now.

This is probably the best course of action

# ? Dec 23, 2014 21:58

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

TLS? No thanks, just deliver to our POP3 server instead :smuggo:

# ? Dec 23, 2014 22:48

vyst: Aug 25, 2009

Gyshall posted:

TLS? No thanks, just deliver to our POP3 server instead

Security is for pussies.

# ? Dec 23, 2014 22:54

goobernoodles: May 28, 2011; Wayne Leonard Kirby.

Orioles Magician.

Anyone know what would cause activesync to poo poo-out only for iphones after server maintenance? I've had to shut everything down including domain controllers and the exchange server a few times in the last month for host/SAN maintenance and each time I had a bunch (not sure if all) of people with iphones needing help getting their email working again. Turning syncing off and back on seems to do the trick. Annoying as hell.

# ? Dec 24, 2014 01:57

Gyshall: Feb 24, 2009; Had a couple of drinks.
Saw a couple of things.

Sounds like something fucky with the Client Access role. Alternatively, if those users are members of certain built in security principals (like Domain Admins, Enterprise Administrators etc) Exchange might have trouble reading permissions on their Active Directory user object.

I'd check the patch level of your Client Access server and update to the latest service pack and update rollup 7 for SP3 if you can.

# ? Dec 24, 2014 04:36

Adbot: ADBOT LOVES YOU

# ? May 7, 2024 06:56

AlternateAccount: Apr 25, 2005; FYGM

Filthy Lucre posted:

The email account filthy.lucre@fuckedup.company resides on both the lovely POP3 server and our Exchange Server. The lovely POP3 server is our MX server of record.

When you email filthy.lucre@fuckedup.company, it is received by the lovely POP3 server.
Our Exchange server checks the filthy.lucre@fuckedup.company account via a non-AD aware POP3 connector.
My Outlook connects to our Exchange Server and I get my email.

The problem is, our current POP connector cannot deal with changes in AD passwords. So we either have to disable the password change policy (not feasible), or users have to notify IT staff every time they change their domain password so we can update the POP connector (kill me).

The easiest and best solution would be to return the Exchange server to our MX server of record. Our Exchange Server is functioning perfectly fine and there's no reason to migrate. However, the CEO of some small IT Consulting Business who is "good with computers" plays golf with our parent company's CEO and talked our CEO into buying this lovely POP3 server. Since the company spent the money on this lovely software, it's a corporate decree that we must use it so our CEO doesn't look like an idiot. Meanwhile, we as IT staff, have to keep email/calendaring running as smoothly as possible. Since the POP3 software is poo poo, that means keeping our users on Exchange and letting the Exchange server get the emails from the POP3 server.

The second best solution is to replace our current POP3 connector with one that is AD aware so we don't have to change the password policy or update the POP connector every time someone changes their password.

My god, dude. Just change the MX record to point to Exchange and file it under "nobody's gotsta know." It sounds like if the POP3 server is sitting there idle and being bypassed, there would be no change to the end user experience?

# ? Dec 30, 2014 17:56

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > Exchange - where email goes to die

«‹›97 »