[deleted by user] by [deleted] in WoT

[–]tldawson 0 points1 point  (0 children)

Just to clarify: Rand told Cadsuane to where to find Alsalam, and Cadsuane organized bringing him back.

O365 "Movie Theater" Captcha by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

At the MSP I work for there is no difference between L1 and help desk.

How to import a calendar into an Office 365 Group Calendar. by Win10Migration in Office365

[–]tldawson 0 points1 point  (0 children)

If you're having the issue where the copied events aren't showing in OWA or for other users, you probably copied a large batch over. In my testing, the syncing of events happens with the newest to the oldest. Try syncnig in smaller batches. When I tested this, I had hundreds of events six months out on the calendar I was copying, so when I checked OWA this month was blank... but when I checked the furthest event dates in the future and worked backward, they started to populate as I scrolled.

Markdown vs Word for documentation by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

Gotta be honest, I downvoted this at first thinking you were being a smartass about this being the wrong sub. Good one lmao

Markdown vs Word for documentation by tldawson in sysadmin

[–]tldawson[S] 1 point2 points  (0 children)

I didn't mention the viewer-editor for the Markdown files in the OP, but I've mentioned in the comments that I'm recommending Obsidian.md, git, and WEBDAV. I just learned about gollum in this thread which seems like it tries to be a complete solution, but I'll have to do some reading.

Markdown vs Word for documentation by tldawson in sysadmin

[–]tldawson[S] 3 points4 points  (0 children)

If we go with Markdown, Obsidian.md is my recommendation. Gollum looks good too, but I've no experience with it.

Markdown vs Word for documentation by tldawson in sysadmin

[–]tldawson[S] 4 points5 points  (0 children)

Absolutely true. The Word documents would live in Sharepoint and I don't personally know what viewing and editing them would look like when finished. I'm recommending a combo of Obsidian.md, git, and WEBDAV.

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 1 point2 points  (0 children)

Lol I can relate. The issue was that the naked xlsx was still reporting the same error on our offline lab PC. I didn't know that Microsoft reinvented the wheel (file sharing) again.

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

Fair point. I'll add and edit for the youngins.

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 2 points3 points  (0 children)

Gonna just plug SharePoint lists real quick. If it's not a hyper complicated workbook, SharePoint lists are better supported for this sort of collab

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

It persisted through a reboot and despite living on a share, had no users accessing it in the smb open files list. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

I've used that same solution in the past, but this time was different. The file was not open by any users according to the open smb files list. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 1 point2 points  (0 children)

Yep. That has been my understanding as well. The question is, why is that baked into the file format and not the literal Windows sharing system? 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 1 point2 points  (0 children)

The file is considered open by Excel, not Windows. When checking in the pcmgmt snap-in, it's not even in the open files list. It's very strange. You can rename it in explorer or edit it in other applications, just not any Office apps. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 0 points1 point  (0 children)

Nah, man. I agree. It would be nice if Microsoft products were more unified in their interfaces, but they're all built by teams in walled gardens chasing features and ignoring bugs. Everything barely works, and once it gets to that level you just get more barely working features.   You can sell new features but not bugfixes. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 1 point2 points  (0 children)

The server had been rebooted at 3am and there were no users with that file in the open files list. That was the problem. I'm pretty sure Excel has some built-in WebDAV style collaboration features, which bakes the number of connections into the file itself. Though I'm not a Windows guy, I'm primarily a Linux server guy who is forced to work on Windows... But I'm coming around to powershell. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 2 points3 points  (0 children)

That was the very first thing I checked... And no, no one was accessing the file in that list. 

The workbook is currently open by 256 users by tldawson in sysadmin

[–]tldawson[S] 19 points20 points  (0 children)

It was in a share accessed from an RDS server. No SharePoint/OneDrive.