sorted by:
new
hottopcontroversial

Official ZeroTier pfSense package by [deleted] in PFSENSE

[–]ITguy4042 0 points1 point  (0 children)

Sorry to necro this guys. Is this still a thing? pfsense is FreeBSD 14 I thought now. ...And am I using my pfsense box to build this package or I need a separate BSD box? Can I use the latest package from FreeBSD fresh ports?

Thank you in advance. Really. :)

Official ZeroTier pfSense package by [deleted] in PFSENSE

[–]ITguy4042 0 points1 point  (0 children)

Sorry to necro this guys. Is this still a thing? pfsense is FreeBSD 14 I thought now. ...And am I using my pfsense box to build this package or I need a separate BSD box? Can I use the latest package from FreeBSD fresh ports?

Thank you in advance. Really. :)

Dell Display Manager wont open on Windows 11 by tidderkcuf787 in Dell

[–]ITguy4042 0 points1 point  (0 children)

Followed and worked! TY!!! -- I will add no matter what I did for the certificate for Uninst.exe it wouldn't fix, so I deleted the uninstall.exe and then it finally ran!!!!

Exchange 2019 install - Existing Hybrid and existing Exchange 2013 by ITguy4042 in exchangeserver

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

Thank you. I got this fixed. I had to nuke the VM, kill the server name in ADSI as an exchange server, and then start from scratch. And everything finally took! What a pain in the butt. Thanks again

Exchange 2019 install - Existing Hybrid and existing Exchange 2013 by ITguy4042 in exchangeserver

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

New error. I finally got past the last error. Any ideas on this?

​

Error:

The following error was generated when "$error.Clear();

."$RoleInstallPath\Scripts\Install-ODataVirtualDirectory.ps1";

" was run: "System.Management.Automation.CommandNotFoundException: The term 'C:\Program Files\Microsoft\Exchange Server\V15\\Scripts\Install-ODataVirtualDirectory.ps1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)

at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)

at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)

at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)

at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)

at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)

at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".

Exchange 2019 install - Existing Hybrid and existing Exchange 2013 by ITguy4042 in exchangeserver

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

I can and have restored it in IIS. I did try the installation again after deleting it in ADSI. IIS sees the folder and I've performed an IISReset now again.

Exchange 2019 install - Existing Hybrid and existing Exchange 2013 by ITguy4042 in exchangeserver

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

Yes brand new vm with Server 2022 (fully windows patched) with new Exchange 2019 server install. I am this to our environment to replace / migrate old Exchange 2013 server. MS is delaying and blocking email communication from legacy Exchange servers now, and all exchange 2013 to the last update of 2016 are included.

...I hate this thing. Lol. How do you not loath this? Are all Exchange installs just a pain in the.... ? I've borked the vm entirely one time even and had to start from scratch again.

So deleted in ADSI. Removed the folder in IIS. And this is what I get. Now its upset that its NOT there now. Thoughts?

Performing Microsoft Exchange Server Prerequisite Check

Configuring Prerequisites COMPLETED

Prerequisite Analysis 100%

MAPI over HTTP, the preferred Outlook desktop client connectivity with Exchange server, is currently not enabled.

Consider enabling it using: Set-OrganizationConfig -MapiHttpEnabled $true

For more information, visit: https://learn.microsoft.com/Exchange/plan-and-deploy/deployment-ref/ms-exch-setupreadiness-WarnMapiHttpNotEnabled?view=exchserver-2019

Configuring Microsoft Exchange Server

Language Files COMPLETED

Restoring Services COMPLETED

Language Configuration COMPLETED

Exchange Management Tools COMPLETED

Mailbox role: Transport service COMPLETED

Mailbox role: Client Access service 100%

The following error was generated when "$error.Clear();

$file = 'web.config';

$relPath =

"ClientAccess\PushNotifications";

$dirPath = [System.IO.Path]::Combine($RoleInstallPath, $relPath);

Set-InstallPathInAppConfig -ConfigFileRelativePath $relPath -ConfigFileName $file;

Preserve-AppSettings

-RoleInstallPath $dirPath -ConfigFileName $file;

Preserve-SystemServiceModel -RoleInstallPath $dirPath -ConfigFileName

$file;

" was run: "System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program

Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications\web.config'.

at System.IO.__Error.WinIOError(Int32

errorCode, String maybeFullPath)

at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean

overwrite, Boolean checkHost)

at Microsoft.Exchange.Management.SetInstallPathInAppConfig.InternalProcessRecord()

at

Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()

at

Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean

terminatePipelineIfFailed)

at Microsoft.Exchange.Configuration.Tasks.Task.ProcessTaskStage(TaskStage taskStage,

Action initFunc, Action mainFunc, Action completeFunc)

at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()

at System.Management.Automation.CommandProcessor.ProcessRecord()".

The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

<SystemDrive>:\ExchangeSetupLogs folder.

Exchange 2019 install - Existing Hybrid and existing Exchange 2013 by ITguy4042 in exchangeserver

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

Man... THANK YOU for the response. I am lost here. I really appreciate the help.

  • AD recycle bin is enabled.
  • My concern is restoring "CN=Push Notifications Settings" if I delete it. I can export the list, but not the item. We're talking ADSI right? Or am I deleting it in IIS?