Re: Store.exe Version
From: Marc Nivens [MSFT] (marcn_at_online.microsoft.com)
Date: 04/07/04
- Next message: Regina Lim: "M Drive suddenly disappear and reappear"
- Previous message: Malvin M. Seale [MSFT]: "Re: store not starting"
- In reply to: piers adderley: "Re: Store.exe Version"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 7 Apr 2004 01:58:51 -0500
My next guess is that we're dealing with some sort of mailbox cache issue.
If I'm correct, then a restart of the Information Store service should make
the limits take effect. If that is the case, then this article should help
fix the problem:
327378 XADM: Exchange 2000 Mailbox Size Limits Are Not Enforced in a
Reasonable
http://support.microsoft.com/?id=327378
In the meantime I will see what else I can find on this just in case this
doesn't resolve your issue.
-- Marc Nivens Enterprise Messaging Support This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "piers adderley" <anonymous@discussions.microsoft.com> wrote in message news:18d9a01c41bbc$31709580$a401280a@phx.gbl... > ah, ok. thanks. > > From what you said, i think i'm probably just confused > over the difference (or maybe similarities) between ADSI > and CDOEXM. The code i used is below, which is the same > way as you're example? This works, in that it sets the > value correctly in the AD, but this is never picked up by > the store. Any other ideas about what else i might try? > As mentioned, the quota value change in the AD *always* > gets pushed through to the store if the change is made > with the GUI, so i was thinking along the lines of trying > to programmatically recreate exactly what the GUI is > doing.. Do you have any idea what the GUI might actually > be doing when it makes the change? Thanks for your help so > far.. > > Set args = WScript.Arguments > > If args.Count < 1 Then > WScript.Echo "Usage: quota.vbs <USERNAME> > [HardLimit] [OverQuotaLimit] [StoreQuota]" > WScript.Quit > Else > strNTName = args(0) > > Set rootDSE = GetObject("LDAP://RootDSE") > > Set objTrans = CreateObject("NameTranslate") > objTrans.Set 1, rootDSE.get("defaultNamingContext") > strNTdomainName = objTrans.get(3) > > Set objTrans = CreateObject("NameTranslate") > objTrans.Set 3, strNTdomainName & strNTName > strUserDN = objTrans.Get(1) > > Set objUser = GetObject("LDAP://" & strUserDN) > > WScript.Echo "" > WScript.Echo "Retrieving via LDAP For: " & > strUserDN > WScript.Echo "" > WScript.Echo "Hardlimit : " & objUser.Hardlimit > WScript.Echo "OverQuotaLimit: " & > objUser.OverQuotaLimit > WScript.Echo "StoreQuota : " & > objUser.StoreQuota > WScript.Echo "" > WScript.Echo "" > > If args.Count = 4 Then > WScript.Echo "You passed some new limits - > attempting to set..." > objUser.Hardlimit = args(1) > objUser.OverQuotaLimit = args(2) > objUser.StoreQuota = args(3) > objUser.EnableStoreDefaults = False > objUser.SetInfo > WScript.Echo "...Done. LDAP Query now > reports:" > > Set objUser = GetObject("LDAP://" & > strUserDN) > > WScript.Echo "" > WScript.Echo "Retrieving via LDAP For: " & > strUserDN > WScript.Echo "" > WScript.Echo "Hardlimit : " & > objUser.Hardlimit > WScript.Echo "OverQuotaLimit: " & > objUser.OverQuotaLimit > WScript.Echo "StoreQuota : " & > objUser.StoreQuota > WScript.Echo "" > WScript.Echo "" > End If > End If > > > >-----Original Message----- > >Unless you're talking about the post sp3 september > rollup, we generally do > >not just publish every new version of store.exe that we > make to the web. > >The ones that are not part of a service pack or rollup > usually fix very > >specific issues, and I'm not aware of one for your case. > It would appear > >that you have one of the most recent versions already > anyway. > > > >Short of actually having the script you're using I can > only speculate. I > >will say that I've seen issues setting this value with > ADSI as opposed to > >CDOEXM because there are some checks that CDOEXM does > that ADSI simply does > >not. Just in case you were wondering, the sample to set > this via CDOEXM is > >something like this: > > > >Dim oMailbox As IExchangeMailbox > >Dim oUser As IADsUser > > > >Set oUser = GetObject("LDAP://" & DNOfUser) > >Set oMailbox = oUser > >oMailbox.EnableStoreDefaults = False > >oMailbox.StoreQuota = 45000 > >oMailbox.OverQuotaLimit = 50000 > >oMailbox.HardLimit = 55000 > >oUser.SetInfo > > > >Again, this may or may not be your issue but It's at > least worth trying. > > > >-- > >Marc Nivens > >Enterprise Messaging Support > > > >This posting is provided "AS IS" with no warranties, and > confers no rights. > >Use of included script samples are subject to the terms > specified at > >http://www.microsoft.com/info/cpyright.htm > > > > > >"piers adderley" <anonymous@discussions.microsoft.com> > wrote in message > >news:1869701c41b1a$92eece00$a401280a@phx.gbl... > >> er...yeah. thanks. i realise how to find the store > version > >> that we're currently using (you might have noticed that > i > >> mentioned the version number in the question). I was > >> actually interested in finding the latest version > >> available from microsoft. > >> > >> Thanks, also, but again i'm aware of the necessary > >> dependancies of also setting the mDBUserDefaults value > to > >> false. Needless to say i had done this. > >> > >> To re-iterate, the problem i have is when i ldifde > import > >> quota values into the Active directory (and also check > >> that these values have been set correctly using the > >> management gui), these values are never picked up and > used > >> by the store. Whereas changing the values in the gui, > say > >> by 1kb, will make the store realise a change has been > made. > >> > >> I have also tried using ADSI in a VBscript to change the > >> quota values, because i thought this would more closely > >> follow the process that the gui goes through when a > quota > >> value is changed. The script was successful, in that it > >> changed the value in the active directory, but again the > >> store ignored the change. (again, after giving plenty of > >> time, changing the value by 1kb in the gui worked). > >> > >> I have also consulted the following KB > >> http://support.microsoft.com/default.aspx?scid=kb;en- > >> us;326252&Product=exch2k > >> We are running a later version of the store (as detailed > >> in my first post) and have the relevant registry values > >> set. Also the problem we are seeing is that the mailbox > >> size limits are not enforced at all, rather than not > >> enforced in a reasonable amount of time. > >> > >> > >> >-----Original Message----- > >> >You can find the store.exe version by right clicking on > >> the file and getting > >> >properties (its on the version tab). However, what > >> you're describing > >> >doesn't sound like a store problem. Its more than > likely > >> an issue with the > >> >LDF import. Keep in mind that if you are using ldifde > to > >> modify the > >> >send/receive limit, modifying mDBStorageQuota, > >> mDBOverQuotaLimit, and > >> >mDBOverHardQuotaLimit alone isn't sufficient. Users by > >> default will have > >> >mDBUseDefaults set to true, which tells store to ignore > >> user level quota > >> >limits and use the IS defaults. So basically, in > >> addition to modifying the > >> >quota limits you will also need to set mDBUseDefaults > to > >> false. > >> > > >> >-- > >> >Marc Nivens > >> >Enterprise Messaging Support > >> > > >> >This posting is provided "AS IS" with no warranties, > and > >> confers no rights. > >> >Use of included script samples are subject to the terms > >> specified at > >> >http://www.microsoft.com/info/cpyright.htm > >> > > >> > > >> >"Piers Adderley" <piers_adderley@hotmail.com> wrote in > >> message > >> >news:173aa01c4189b$fef84ee0$a301280a@phx.gbl... > >> >> Hi, > >> >> i was just wondering how i would find out what the > >> latest > >> >> version of the store.exe is (and its associated dll's > >> >> etc.). We're currently running with 6.0.6521.0 , but > are > >> >> seeing problems where the store is not enforcing > mailbox > >> >> quota values that are imported into the AD with > Ldifde - > >> i. > >> >> I've also tried changing the AD quota values with an > >> ADSI > >> >> VBscript, but run into the same problems. It seems > the > >> >> only way to make the store pick up the change is to > >> change > >> >> the AD value with the ADU&C GUI. > >> >> Any ideas? > >> > > >> > > >> >. > >> > > > > > > >. > >
- Next message: Regina Lim: "M Drive suddenly disappear and reappear"
- Previous message: Malvin M. Seale [MSFT]: "Re: store not starting"
- In reply to: piers adderley: "Re: Store.exe Version"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
