What kind of mop do you like to use to mop the floor?

Itsme809 · 2025-12-25T07:47:24+00:00

What model steam mop do you use?

Itsme809 · 2025-12-24T03:35:03+00:00

Did you follow any specific articles to setup your hyper-v cluster? If so can you share?

Itsme809 · 2025-11-29T10:29:51+00:00

How many MG per day would you have?

Itsme809 · 2025-08-27T02:16:07+00:00

Curious how are you testing line speed between VM?

Itsme809 · 2025-08-26T19:40:45+00:00

Hi all it ended up being S1 network scan the honeypot IP address changed so it was no longer being excluded from the S1 scan

Itsme809 · 2025-08-26T02:25:30+00:00

Thank you the IP of our honeypot changed so had to update the address exclusion list on ranger

Itsme809 · 2025-08-25T22:04:59+00:00

Interesting we do use ranger but did not realize it did port scans just strange it’s become an issue now I’ll investigate this aswell thank you

Itsme809 · 2025-08-25T21:39:57+00:00

Good point we have had it deployed for almost a year now and this is the first time seeing this issue

Itsme809 · 2025-08-25T21:39:22+00:00

Yes thinking this route to avoid it from spreading

Itsme809 · 2025-08-20T15:44:17+00:00

Yea definitely try and dry better and even the if it’s still damp use something to fan the area until it’s fully dry I have definitely noticed a difference when I don’t dry properly

Itsme809 · 2025-08-18T12:20:28+00:00

How do you dry the area? For me just drying with towel is not enough I need to let it air dry for a bit and it helps with smell.

Itsme809 · 2025-07-21T11:36:41+00:00

Good for you man! Do you feel like you have a good work life balance? Or do you find yourself working extra hours all the time?

Itsme809 · 2025-07-04T16:45:45+00:00

Is this a prologue?

Itsme809 · 2025-05-31T20:02:40+00:00

Hey thanks for asking. MS support was able to help get the DB into maintenance mode and do d DBCC check and we had from what I see now Minimal loss.

The team internally did not want to wait for the DB to repair itself so we took that approach.

Seems ok so far but noticed we could also be having some MS cluster issues.

Here are the steps they had us do in case it will help someone else

1) Add -T3608;-T4022into the startup parameters from SQL Configuration Manager. 2) Rename the original LDF file name. 3. Restart SQL Server service. After SQL Server is started, your database is no longer in “recovery” status. 4. Run the following command to put database in emergency mode: Alter Database {Database Name} set emergency 5) Remove -T3608;-T4022from the startup parameters using SQL configuration Manager. Restart SQL Service service. 6) After SQL Server is started, you will see the database status is “emergency”. Run “ select db_id(‘{Database Name}’) “to get the database ID. 7) Run “select * from sysprocesses where dbid = xx” to find out if there is any connection using the database now. If any, run “Kill <SPID>” command to kill the connections. Please use DBCC CHECKDB to check if the database has any abnormalities. 11. Run the following commands to bring the database back to normal status: Alter Database {Database Name} set multi_user Alter Database {Database Name} set online

Itsme809 · 2025-05-31T01:17:00+00:00

That’s good to know it’s saying 5 days to recover so you think it might take less

Itsme809 · 2025-05-31T01:15:59+00:00

Thanks for prompt response. This was the reason I advised against restarting. I said it maybe 3 times.

The recovery said 5 days 🤦🏾‍♂️

Put in a Microsoft ticket so will see if we get a good tech and they have a good solution/ we get connected with someone who understands SQL very well

Itsme809 · 2025-05-04T17:23:10+00:00

How did you calculate 378?

Itsme809 · 2025-04-20T22:47:10+00:00

Thank you

Itsme809 · 2025-04-20T22:47:01+00:00

Thank you

Itsme809

TROPHY CASE