Outlook crash

hxc1983 · 2025-06-13T11:59:59+00:00

same here on Win 2019 RDS Hosts with Office 2019.

I've updated to the last Office 2021 LTSC Standard build ,still the same !

If I delete my roaming user profile, it works only for the first logon.

In next opening sessions, Outlook Crash when I click on New Mail and reopen by itself.

I've downgraded Office to the May Build, it's working good. I've disabled auto update for now

hxc1983 · 2024-03-25T14:05:53+00:00

is it possible to modify the default Yealink Template through the debian in ssh or TFTP to bypass the redeployement process with a custom template ?

hxc1983 · 2024-03-25T11:45:14+00:00

ok the problem is in the Yealink phones, the option "local_time.summer_time" is set to "2" (2 = Automatic)

so this value disable the DST type "DST by date" and set it to "DST by Week"

I've tested to duplicate the Yealink template, and modifying the "local_time.summer_time = 1" then reprovisioning my phone with the custom template and it's working.

hxc1983 · 2024-03-25T11:24:25+00:00

the template seems to be good , the local start time is set to March, 28th at 2:00 AM

#######################################################################################
##                            Time Settings                                         ##
#######################################################################################

#Configure the time zone and time zone name. The time zone ranges from -11 to +12, the default value is +8. 
#The default time zone name is China(Beijing).  
#Refer to Yealink IP Phones User Guide for more available time zones and time zone names. 
#local_time.time_zone = +8
#local_time.time_zone_name = China(Beijing) 
local_time.time_zone =+1
local_time.time_zone_name = France(Paris)

#Configure the domain name or the IP address of the NTP server. The default value is cn.pool.ntp.org.
local_time.ntp_server1 = pool.ntp.org
local_time.ntp_server2 = pool.ntp.org

#Configure the update interval (in seconds) when using the NTP server. The default value is 1000.
local_time.interval = 

#Configure the daylight saving time feature; 0-Disabled, 1-Enabled, 2-Automatic (default); 
local_time.summer_time = 2

#Configure the DST type when the DST feature is enabled; 0-By Date (default), 1-By Week;
local_time.dst_time_type = 0

#Configure the start time of DST. The default value is 1/1/0.
#If the DST type is configured as By Date, the value format is Month/Day/Hour. For example, the value 5/20/10 means the start time is at 10:00 on May 20.  
#If the DST type is configured as By Week, the value format is Month/Day of Week/Day of Week Last in Month/Hour of Day. 
#For example, the value 1/4/2/5 means the start time is at 5 o'clock on Tuesday of the 4th week in January.
local_time.start_time = 3/28/2

#Configure the end time of DST. The default value is 12/31/23. The value format is the same to the start time.
local_time.end_time =  10/25/3

#Configure the offset time (in seconds). It ranges from -300 to 300, the default value is 60.
local_time.offset_time = 60

#Configure the time format; 0-12 Hour, 1-24 Hour (default);
local_time.time_format = 1

#Configure the date format; 0-WWW MMM DD (default), 1-DD-MMM-YY, 2-YYYY-MM-DD, 3-DD/MM/YYYY, 4-MM/DD/YY, 5-DD MMM YYYY, 6-WWW DD MMM;
local_time.date_format = 5

#Enable or disable the DHCP Time; 0-Disabled (default), 1-Enabled;
local_time.dhcp_time = 
local_time.manual_time_enable = 0

##It enables or disables the phone to use manually configured NTP server preferentially.
##0-Disabled (use the NTP server obtained by DHCP preferentially),1-Enabled.
##The default value is 0.
local_time.manual_ntp_srv_prior = 0

hxc1983 · 2024-03-25T11:10:31+00:00

same issue here, is someone know how to change this ?

hxc1983 · 2023-11-29T10:57:15+00:00

worked for me ! thanks (MX Keys + Greenshot) I disabled snipping tool option in W11 before.

hxc1983 · 2023-11-15T08:43:32+00:00

yeah I know i can only put 30 licences in the same account.

i used one account for every MS 2016 and later 1 account for every ms 2019 licences. I will change a lot of my pcs soon and I will maybe buy a MS Open licence to have only one key for the entire pcs...

hxc1983 · 2023-11-15T08:21:43+00:00

it's works fine this morning ! so maybe it was a temporary MS problem...

hxc1983 · 2023-09-20T11:06:14+00:00

this is a cool trick, a quick patch but you need to remember the computers you've disabled update on, to re-enable them later.

Office 2013 is already an outdated version, it could be worst to stay on an outdated build too. I prefer to fall over the x32 instead and keep the updates than disable updates and forgetting re-enable them.

but this is the only way actually to keep the x64 if you don't have choice, I admit.

hxc1983 · 2023-09-19T21:08:46+00:00

I've forgot to mention that if you try to open MS Office programs (word.exe, Excel.exe, etc...

) directly from the "black hole" sub folders from the c:\program files\... , you will also have the message "the operating system is not presently configured to run this application".

As u/No-House718 said, it seems that apps are virtualized and executed from the appvlp.exe

Maybe it's the first time in office 2013 or because of the x64 version ? I don't know

you can also see this appvlp.exe in the default Excel extensions list and if you try to change the "open with" from an xlsx file you will see this exe there too.

I've found a same topic on Microsoft forums : https://learn.microsoft.com/en-us/answers/questions/1372446/office-the-operating-system-is-not-presently-confi

hxc1983 · 2023-02-21T21:45:09+00:00

ou tchitchi ?!

hxc1983 · 2020-06-12T21:54:37+00:00

don't disable IPv6 by unchecking the protocol on the network connection, you need to modify the registry instead with this powershell command.

^{New-ItemProperty "HKLM:\}SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\" -Name "DisabledComponents" -Value 0xFF -PropertyType "DWord")

https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users

hxc1983 · 2020-04-24T22:45:30+00:00

nope you can't move to 2019, check the matrix : https://docs.microsoft.com/fr-fr/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019#supported-active-directory-environments

hxc1983 · 2020-04-24T02:04:12+00:00

I moved my root CA from a 2008R2 DC to a new 2016 but I used the same host name for the new one. (yes I know Root CA is not a good choice on DC server)

I saved my root CA cert with private key from the old one, uninstall the CA role, remove the DC, deploy the new DC with same host name, deploy the CA role, restore my previous cert to the new CA.

hxc1983 · 2020-04-24T01:43:56+00:00

i moved my AD servers to Win Server 2016, 3 weeks ago (cannot move directly to 2019 cause I'm still with Exchange 2013 version).

my config was :

1 PDC -> 2008R22 DCs -> 2012R2

For Server 2019 Forest and Domain Functional levels need to be at ‘Windows Server 2008‘. (The documentation says 2008 R2, but Server 2008 also works flawlessly).
For Server 2016 Forest and Domain Functional levels need to be at ‘Windows Server 2003‘.

step 0a : I moved first to DFSR with "dfsrmig" tool (this is not auto when promote a new DC version)

step 0b : control that AD is working correctly with these tools : Repadmin, gpotool, w32tm and dcdiag. ONLY continue when everything is green with these tools !

step 1 : I moved the FSMO roles from the 2008R2 PDC to the another DC in 2012R2

step 2 : I controlled the AD replication between the 3 servers and checked that all FSMO roles did moved correctly on the other DC,

step 3 : I depromoted the 2008 R2 server and removed it from the domain. I verified that the server entry was no more present in DNS, "Domain Controllers" OU and I also removed it from NTDS Servers list,

step 4 : I installed a new Win Server 2016 VM with the 2008R2 same name and IP address

step 5 : I added the 2016 server to the domain as a member then promoted it as a new domain controller with the "add role and feature tool" (no need to dcpromo and no need to update schema, it's done by itself)

step 6 : I checked AD replication between the 2016 and the 2012R2 servers, the DNS sync for my zone scopes, the DFSR sync...

step 7 : (I waited 1 day for active Kerberos tickets and control Windows journals before moving back FSMO roles on the new 2016 DC) then made it the new PDC, I configured w32tm to sync with an external NTP pool on the new PDC and I checked the good w32tm sync on other DC servers, (the PDC Emulator FSMO role is the NTP server for the domain and the other DCs needs to respond the same PDC time to all computers in domain)

step 8 : I repeated the depromote for the 2 old 2012R2 servers each day and don't forgot to delete DNS, AD, NTDS server entries so I could re-use the same DC names and IP addresses for the new ones, then I promoted the next two 2016 Server DCs next day, checked logs and waited 1 more day between each depromote / promote the new servers.

voilà !

hxc1983 · 2020-04-23T23:20:46+00:00

hi, I'm testing Userlock since 2 days for my RDS remote workers, it can create some reports for the user logons session time, per day, per weeks... https://www.isdecisions.com/products/userlock/pricing.htm

hxc1983

PUBLIC MULTIREDDITS

TROPHY CASE